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.







-
View User Profile
-
Send Message
Posted Jun 2, 2013Hello i get this error on the new dev build on join:
using spigot
5:52:54 PM CONSOLE: [WARNING] Failed to initialize a channel. Closing: [id: 0xd876806d, /71.168.208.228:59407 => /192.30.138.250:25565]
-
View User Profile
-
Send Message
Posted Jun 2, 2013@freakyy85 Confirmed, and I am now looking into this. Fix will be added for BKCommonLib once I find one.
EDIT
Those that had issues with bPermissions: please check whether the current latest BKCommonLib build fixes your issue.
-
View User Profile
-
Send Message
Posted Jun 2, 2013@bergerkiller
Thanks very much! Just one more thing, your plugin has saved my server more times than I can remember, so thankyou for making it! (I also think TrainCarts is the greatest thing ever to happen to bukkit)
-
View User Profile
-
Send Message
Posted Jun 2, 2013hm, for me, i have installed latest dev of bkcommonlib and nolagg, but when i try to use commands it says i dont have permission. i added the permissions to my group but i still cant use the commands. is there a bug?
-
View User Profile
-
Send Message
Posted Jun 2, 2013@Evilbannana1 All right, I believed what you said was sane enough to be implemented, so it is now implemented. You can set a tick rate trigger for the examine report. You can set a TPS threshold and for how many ticks the TPS has to have this value for it to trigger. Then you can set how long the examine report should be, and the minimum interval between two reports caused by this.
See the latest dev-build, and after first restart, the 'tickRateTrigger' section of the examine config.yml.
-
View User Profile
-
Send Message
Posted Jun 2, 2013Oh I realise this, but I have a very large amount of plugins so when one goes severely wrong it can take a long time to identify the issue and get it fixed. Let me explain a situation where this would be useful.
We recently had a problem which caused the server tick rate to drop a lot (roughly 2-3 tps) at random intervals, usually once or twice a day, without putting any errors in the console. These errors would often cause a reboot, as my server host forces servers to reboot if they do not respond to a ping fast enough. This had the effect that unless I was there at the exact time waiting for the error to happen, I would initiate the examine command too late, or not at all, and the server would shut down before I could get anything useful. Eventually I was on at the exact right time, used examine and found that LWC was having some serious issues, and managed to fix the problem within a few hours.
If the examine command had initiated automatically when the lag dropped, I could have found what was causing the problem weeks earlier. The lagNotifier is a great feature, but I'm often not online when the problems occur, and so by the time someone has reported that the notification is coming up, it was too late. I would suggest having the feature I previously mentioned togglable in the config (default off) to avoid it needlessly activating, or even triggering when the TPS is below the threshold for a set period of time, to avoid false positives.
-
View User Profile
-
Send Message
Posted Jun 2, 2013@Evilbannana1 It's possible, but it's very likely that server processes, NOT plugins, cause the server to hang. Things such as teleporting using portals is dreadfully slow, not to mention chunk generation and entity ticking. The tick rate is too much likely to drop below whatever threshold you put, and it makes the feature pretty much worthless.
What you CAN do is enable the 'lagNotifier' in the monitor component to inform players when the tick rate significantly drops. You can then decide for yourself whether to start examining or not.
Note that I can not examine real-time since examining the server DOES bring a performance reduction, since nanotime measurement in Java is particularly slow.
-
View User Profile
-
Send Message
Posted Jun 2, 2013Could you add a setting to the examine function that will automatically start examining if the tick rate drops below a certain threshold? Would make identifying lag-causing plugins a LOT easier.
-
View User Profile
-
Send Message
Posted Jun 2, 2013But nolagg need to much Ram and the BKCommandlib bugs to much..
-
View User Profile
-
Send Message
Posted Jun 1, 2013@dermarionator No need, just disable all other components you do not need in the config.yml.
-
View User Profile
-
Send Message
Posted Jun 1, 2013Can you add an Extra Plugin which only can run /nolagg examine?
-
View User Profile
-
Send Message
Posted Jun 1, 2013please checkout newest huge issue: http://dev.bukkit.org/bukkit-mods/nolagg/tickets/233-player-join-crashes-server/ ty :P
-
View User Profile
-
Send Message
Posted Jun 1, 2013@CommodoreAlpha There is no way currently, but I'll add a simple /lag examine cancel command for you. You can limit the maximum examine time in the config.yml to prevent future problems with this. This maximum is defined as:
Which you should then reduce to 5000 or whatever maximum is possible on your server.
@DiirtyMoneyz What type of lag are we dealing with here? A lot of items are spawned? Hoppers are inefficient, I know, you could use Spigot to alter how often they pick up items to reduce the performance hit.
-
View User Profile
-
Send Message
Posted May 31, 2013A few players on my server have about 25+ mobs trapped inside a cage sitting on hoppers which are collecting the chicken eggs. This is causing quite a lot of lag especially now that more people know of this.
Is there anything in config I can change to prevent this?
-
View User Profile
-
Send Message
Posted May 31, 2013Is there a way to stop a lag examination that's currently in progress? It gets annoying when I meant to scan for 1000 ticks and I accidentally scan for 10000 ticks. Then it gives me an examination file I can't even open, because the file is too big.
-
View User Profile
-
Send Message
Posted May 29, 2013hey i dont know whats happening but i did post a ticket: http://dev.bukkit.org/server-mods/nolagg/tickets/231-random-spam-error-s/ just want to make sure u know cause i am using a spigot build and i cant run nolagg with this error, ty xD
-
View User Profile
-
Send Message
Posted May 28, 2013@bergerkiller
Thanks for your support mate. Best of luck!
-
View User Profile
-
Send Message
Posted May 28, 2013@jacob_vejvoda
-
View User Profile
-
Send Message
Posted May 28, 2013Are you gona update to 1.5.2?
-
View User Profile
-
Send Message
Posted May 28, 2013@DiirtyMoneyzz Hmn since TrainCarts seems to suffer from this too, somewhat, I'm going to have do some tests myself to see how well it's all working. I'll use bPermissions then. Perhaps something broke again in BKCommonLib's permission handling routines.