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.
@LegitCake100
You're not pulling your weight. There is a 1.57, else it wouldn't be listed to begin with. Plus, it would be impossible to build a plugin that depended on a nonexistent version of BKCommonLib... (Therefore, there is a 1.57 version and you're not looking hard enough.) :P
Just because the download for it isn't readily apparent, doesn't mean it's nonexistent. (Did you check the Continuous Integration Server?)
First time, quick question! What is required to be in my plugins to use this? Just BKCommonLib?
16.01 20:56:16 [Server] INFO [20:56:12 WARN]: java.lang.OutOfMemoryError: PermGen space 16.01 20:56:03 [Server] INFO [20:56:00 WARN]: Exception in thread "Thread-38" 16.01 20:55:57 [Server] INFO [20:55:57 WARN]: [Server] What follows is the stack trace of the main thread 16.01 20:55:57 [Server] INFO [20:55:57 WARN]: [Server] Probable Plugin causes: 'BKCommonLib and NoLagg' 16.01 20:55:57 [Server] INFO [20:55:57 WARN]: [Server] The main thread failed to respond after 10 seconds
dude BKCommonLib is fucking 1.56 -.- come on men pls update :/ and it says requires 1.57 and my server errors and says need to update -.- what kind of plugin is this bro :/
If you run Spigot, would this plugin still help with lag or would it mess up some Spigot features or something?
For some reason the save feature is causing a lot of lag, even the threadlock notifier comes up. In timings it shows as Task: TimedWrapper(interval 400). Any idea why? I have used this option before, but currently I am facing serious problems, having no way to regularly save my world.... Also, what is the difference between the 2 types of save in the config, the one timed 400 and 12000?
@Mysticforce12345
please you most be joking right ?
where can i download nolagg for 1.7? here? or can you please give me a link to it.
@BlackflameKRS
"...and when i ran ma server it has a ed over bkcommonlib..."
What's an "ed"?
when i dowload bkcommonlib as u told and when i ran ma server it has a ed over bkcommonlib and nolagg help...............
@Mysticforce12345
Yes.
You run outdated versions.
1.6 builds are ONLY for 1.6.
Get 1.7 builds on our jenkins
@Mysticforce12345
That means they are not working. They are found, but not functioning. Check to make sure they are compatible with your version or there isn't anything conflicting.
the plugin not working for me the commands are not working i have BKcommonlib installed and when i do the /plugins command i found that nolagg and bkcommonlib are highlighted in red is that bad?
@lenis0012
I'm not asking for a fix, but your interpretation was extremely helpful. And it confirmed my suspicions. Thanks.
I was (and still am) running an outdated version of Citizens and Sentry (because I'm still using an "ancient" build of CraftBukkit for "certain" reasons). When I removed Citizens, the server issues stopped. So, that'll help me in debugging the issue, though I suspect I will need to update that plugin soon too.
Was there ever a fix for the /lag clear command in 1.6.4? I'm using this plugin on my 1.6.4 modded server (MCPC+) and the /lag clear command spits out errors in console. Everything else seems to be working fine though
@stutiguias
Most likely outdated dependecy, I will work on it asap
@CommodoreAlpha
Seems like an entity loaidng problem in a chunk.
I dont know accactly how to fix this atm
Sorry if this is an inappropriate place to post this, but I'm not sure where else to ask first (besides the Bukkit forums).
Recently, I've been having weird issues concerning severe CPU spikes and some sort of big memory leak. At first, the server seems to run fine, but then over time, memory and CPU usage start rising to the point that memory usage maxes out and the server crashes.
In addition to one plugin firing a "ChunkLoadEvent" error extremely often at some point, I get this:
Yes, I've tried lag examine, but it points at multiple plugins, not just one plugin, so I suspect an underlying cause to this issue (probably some sort of "domino" effect where one plugin acts wonky, and causes other plugins to respond in kind). I'm just curious as to what the above may mean, so that I may perhaps troubleshoot my problems better.
@Fred6567
Same for me. I can't configure because there is no folder or config.yml
I just downloaded the plugin and there was no Config.yml file or any other .yml file except for the plugin.yml. Is it supposed to be like this? If so, how do i configure the plugin? If not, what can i do to fix this?
Thanks, Fred6567
@stutiguias
the answer of orebfuscator -
@stutiguias: Go
That error shows that NoLagg is passing a bad argument causing an error, so it's the problem of NoLagg. For now, disable the chunk buffer system, and warn them that their reflection method calling is using bad parameters.