NoLagg
Version: 1.90.4 | CB 1.7.2
Quote from lenis0012:NoLagg has not been updated since 1.7.10, for more info, check BKCommonLib
Description
NoLagg is made out of multiple completely separate components which you can enable and disable freely. Together they offer:
- Send chunks more gracefully with lowered network stress and reduced processing spikes Read more...
- Remove entities, resend chunks in case of chunk holes and clean up server memory Read more...
- Examine server tick rate performance with deep view into per-tick processes of the server Read more...
- Stop a large amount of items from spawning and spawn at a later time to avoid frozen clients Read more...
- Stack items with a configurable per-world radius Read more...
- Fix lighting errors that cause clients to recalculate lighting (and thus lag) Read more...
- Keep track of server performance such as entities, tick rate, memory and more Read more...
- Fix various bugs the server has (Patches component)
- Schedule autosaves and force data to be written to disk to prevent data loss on server crash (Saving component)
- Limit the amount of entities allowed to spawn per world or globally Read more...
- Watch events closely to warn when plugins execute main-thread methods from another thread Read more...
- Show a detailed message explaining the cause for a server freeze (lock) [read more]
- New TNT execution algortithm that is not only more efficient, but also avoids server freezes Read more...
Important
When first installing NoLagg, open up config.yml and disable components you do not need. This is very important, as some components may conflict with other plugins you use, or may not function on the type of demand you have. If you get a warning message [Severe] followed up with a stack trace in the log, this has to do with the main thread not having responded within 10 seconds. The warning is NOT an error and is no bug, and not a bug related to NoLagg. To disable this feature, disable 'threadlocknotifier' in the config.yml. This feature is mainly intended to notify you what plugin is causing the server to freeze, may it ever happen. It is used to debug plugins in general, as they may get stuck for whatever reason. If NoLagg DOES show up in there, it is a bug you should report.
FAQ
Separating into jar files
NoLagg consists of multiple components you can individually enable and disable. Reasons for not publishing it as a separate jar file for every component can be read here. Please don't ask to separate the components, I will just link you to here.
Spigot server
Not all components are needed when you use the Spigot server. The ItemStacker, ItemBuffer, Spawn Limiter, Thread Checker and Thread Lock Notifier components are not needed, since Spigot has it's own implementations to deal with that. If you still wish to use one of these components, you can, but it's best to disable the Spigot alternative then.
The other components (such as TNT, Chunks, Lighting, Common, etc.) are not implemented in Spigot (yet?) and offer additional functionality.
PTweaks
Since people keep asking about this, I went ahead and compared the two plugins. I am not going to discuss which is better in functionality, I'm just going to state which features overlap and which do not. Both plugins offer a TNT-lag solving solution, feel free to choose which solution you like better. (the solutions are different) Both plugins also offer a way to change when and how chunks are saved, NoLagg adds to this that you can configure when the server writes data to disk. PTweaks offers a way of showing used memory, NoLagg Monitor too with a bit more information. Again, preference. Chunk Persistence is something PTweaks offers and NoLagg does not. Reason I excluded it from NoLagg is that the implementation used up more processing power than that it solved (I did have this for a while). If you want to give it a try, PTweaks is your answer. Monster Limiter is incorporated in NoLagg as well but then for all entities, and more options. ChunkEdits is a tricky one: NoLagg chunks does something similar, with the difference being that it also changes at what rate chunks are sent, which is the main feature NoLagg chunks offers. In addition, the ability to increase the amount of threads running to process chunk packets and the re-using of packet raw data offers some benefits PTweaks does not offer.
Then there are a lot of other features NoLagg has and PTweaks does not, such as examining server tick rate, item stacker, item buffer, fixing lighting, cleaning up server memory, resending chunks, removing entities on command and others (see description).
In short: Both plugins offer some overlapping features, and you need to pay close attention to the configuration of PTweaks and NoLagg and disable things that conflict. Having two TNT explosion altering plugins is going to have strange results, for example. Compare the functionality, decide, and enable in NoLagg what you do not want in PTweaks, and vice versa.
NoLagg showing up in error stack traces
The examine component inserts various hooks into the server to gather measurements. Specifically, you will find that the following lines show up now and then. These hook classes do absolutely nothing when not examining and can not be the cause for any issues, unless the stack trace ends there (first line after the exception shows this stack trace)
- org.timedbukkit.craftbukkit.*
- com.bergerkiller.bukkit.common.internal.ChunkProviderServerHook
Video
Here is a video by BlueDevonMovies (lenis0012):
Metrics
This plugin sends server count statistics to MCStats.org. You can (globally) opt out in the PluginMetrics/config.yml file.
This plugin helped alot on 1.8.1 but I am trying to use the test build for 1.0.0 and upon starting the server I got this error:
@GravelSocks
I will say that you need to update the the latest build of NoLagg 1.49.3.
And...the server is running 1.0.0 - just saw the caveat on the main page. (Kind of lame that we can't edit posts here.)
Hey - noticing a problem with what looks like a memory leak. I am running 1.49.2 and seeing this error repeat over and over:
07:06:02 [SEVERE] java.util.ConcurrentModificationException 07:06:02 [SEVERE] at java.util.HashMap$HashIterator.nextEntry(Unknown Source) 07:06:02 [SEVERE] at java.util.HashMap$KeyIterator.next(Unknown Source) 07:06:02 [SEVERE] at net.minecraft.server.World.a(World.java:2334) 07:06:02 [SEVERE] at net.minecraft.server.ChunkLoader.a(SourceFile:140) 07:06:02 [SEVERE] at net.minecraft.server.ChunkRegionLoader.a(SourceFile:84) 07:06:02 [SEVERE] at net.minecraft.server.ChunkProviderServer.saveChunk(ChunkProviderServer.java:152) 07:06:02 [SEVERE] at com.bergerkiller.bukkit.nolagg.ChunkOperation.execute(ChunkOperation.java:140) 07:06:02 [SEVERE] at com.bergerkiller.bukkit.nolagg.ChunkScheduler.run(ChunkScheduler.java:137)
This error appears once about every 30-45s.
Also - I had a problem with 2 users who thought it was a good idea to set off a 17000 block TNT explosion that was unrecoverable until I removed NoLagg - it kept generating out of memory errors. Server has 4Gb allocated to MC. To make matters worse, they set it off over the ocean and blew away blocks down to bedrock in about a 100+ block radius with splash damage out to 200-ish - so there may have also been issues with water block updates on top of the fact that the biome was trying to freeze everything at the same time.
I will update to 1.49.3. But...may be worth a look if you haven't already fixed something that would improve the above scenario.
I keep getting an error:
What does this mean, and how can I fix it? It's being spammed every save interval.
lol 2100 items from my log seriously?
We have places minecarts and boats we don't want to get rid of nor death drops.
We also have 8000 mobs
When I /butcher 7000+ of them gets killed.
I was hoping to use the mob/animal spawn limits just to set the upper limit to 5000-6000 global that's all and mby items also then.
I won't want any other limiting apart from a global ones as above.
@drguild
Yep, after a certain time you have 2100 items hanging around on the server O_o You can use /nolagg clearall items to get rid of them.
@Pantheis sorry late-night build, reuploading it in a sec.
I just installed NoLagg 1.49.3 and upon logging in, I'm greeted by nothing, and about 1-10 chunks every couple of seconds loading. I have spout 510 installed, CB1337 and Minecraft 1.8.1.
Any ideas?
For spawn limits are default internal minecraft or this:
I have a need to just set the upper limit globally and each world regardless of individual mobs and animals so whats the best way to do this?
Can you see anything unusual with this?
http://pastebin.com/raw.php?i=9TReS0p6
This was taken when cpu was reading
16:28:01 [WARNING] Can't keep up! Did the system time change, or is the server overloaded?
We put this in in hopes we could curb cpu usage problems we cant figure out instead it seems we can only support 4 players before getting 100% cpu when it was 8 players.
Despite having this system on dedicated hosting.
1 x Intel Core 2 Quad Processor Q9550 2.83GHz 1333MHz 12MB LGA775 CPU ()
As well as 8gb of DDR2 775.
Some ram was allocated to a ramdisk we made for map files to help bring down cpu but no luck there either.
@godgodgodgo
Mh seems it uses the Dev bukkit download link there, which is present. Only difference is that I have a zip file here. (I have to, the two together are the same plugin with the only difference being a Spout dependency)
I was just logging in to ask you about signs not showing text and blocks not dropping in 1.4.8, and it looks like you already caught it. I'll try the new version. :)
@bergerkiller
CraftBukkitUpToDate
@TechCraft
Neh I simply won't add it. If it doesn't fit the plugin, I won't add it. Then, at some point, every single plugin 'has' to have it, and that would result in copying the same updater class in all plugins. I rather wait for someone to publish a plugin updater plugin or a section in CraftBukkit.
Also, updated it to v1.49.2 for those interested. Some simple memory improvements for NoLaggChunks and an attempt to fix the final bits of blank signs received by clients.
Could you at least add a config to say: don't notify me on update: true
@TechCraft
Having an updater in every plugin is kinda useless, I'd rather wait for Bukkit (or another plugin) to add update support (maybe through BukkitDev), it's easier and more organized to do so.
Does this still alert you when there is a update can't you put a option in the config like update alert: true because i hate update alerts. Or you should put in a auto updater.
@Sayshal
Does 1.48.6 still have this issue? Since last time I checked, all tile entities were properly saved in that version...
1.48 CHESTS AND SIGNS STILL WIPING! DO NOT USE ABOVE 1.45!
Download for 1.48?