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 Sep 2, 2012@Curtis4321
This is nothing I can fix, it is something you have to fix. You are teleporting players from another thread, something you should never ever do. See the many cross-thread access warnings below. Doing that on a singlethreaded server is recipe for disaster.
@GumbyDammit
All right, I fixed some of the drop problems already (I think, it didn't respawn the items properly) I'll look at the dynamic view distance now.
-
View User Profile
-
Send Message
Posted Sep 2, 2012http://pastebin.com/ZEjyVedi
Help please =D Cwarp is out custom plugin which allows us to warp to places.
And NoLagg is causing Chunks not to load.
-
View User Profile
-
Send Message
Posted Sep 2, 2012@bergerkiller
Hope you're feeling better. I still have a void hole at 0,0 with DynamicView enabled. Setting to false removes the hole.
Thanks for your continued efforts.
-
View User Profile
-
Send Message
Posted Sep 2, 2012Almost feel like screaming 'what is it now?!'...but I won't. Sigh, welp here we go again.
Drop problems
Please tell me what component is causing this. Does it go away with the item buffer disabled? Or is the spawn limiter to blame? If it is the spawn limiter, remove all item-related limits from the configuration. Clearly world-based limits for items is a bad idea. If it is a problem in the item buffer, and there there is no clear mass of items in the chunk you are in, then something is wrong. One can very easily spam a lot of items.
Missing chunk at 0.0
I appeared to have fixed that in 1.88.1, if this is not the case, I'll have to look more into this. Maybe there are more problems CraftBukkit added.
And general note:
It is not the plugin, it is the component. NoLagg technically consists of separated code sections that hardly interact with each other. 'NoLagg causes (...)' is not a valid response OR question, it is like saying 'One of my plugins causes (...)'. I can try and think for myself which component it is that could cause it, but often the bugs are so generic that it is hard to find out which to blame. So please, if you have a problem 'with nolagg', state what component it is:
"When I enable the chunks component of NoLagg, I experience a missing chunk at 0.0."
Thank you. I'll look further into the reported stuff. (I was ill the past 2 days, so therefore I couldn't respond within minutes like you got used to for some reason.) (get used to it, college starts tomorrow and I'll be less communicative during these times)
-
View User Profile
-
Send Message
Posted Sep 1, 2012@bergerkiller I tried the latest 1.88.1 with git-Bukkit-1.3.2-R0.1-b2352jnks, and I get some occasional pillars of void. Is there any way to make NoLagg send chunks more aggressively, or force it to resend chunks near me?
@TheDude1972
The difference is easy to miss:
-
View User Profile
-
Send Message
Posted Sep 1, 2012@ohJey
Disable the variable chunk view distance for now. This will fix it. This option is the one causing the 0,0 chunk to be empty if you walk some blocks away from it.
-
View User Profile
-
Send Message
Posted Sep 1, 2012@TheDude1972
look at the build numbers here http://dl.bukkit.org/downloads/craftbukkit
this does work with the latest version but still many bugs that cause more problems with the plugin then without.
-
View User Profile
-
Send Message
Posted Sep 1, 2012Strange how 1.87.5 is voor bukkit R2.0 but the newer 1.88 and up is actually for the older R1.0 release???
Don't see the logic in that but I do hope you will support the later version again in the future, until then I removed this plugin because it's to buggy especially with the drops. :(
-
View User Profile
-
Send Message
Posted Aug 31, 2012@GumbyDammit
Link 1 of the block drop issue: http://dev.bukkit.org/server-mods/nolagg/tickets/109-block-drop-issue/
Link 2 of the block drop issue: http://dev.bukkit.org/server-mods/nolagg/tickets/82-blocks-not-dropping-items-dropped-items-disapearing/
-
View User Profile
-
Send Message
Posted Aug 31, 2012@GumbyDammit
Its not 1.3.2 beta, its been like this since 1.2RB
-
View User Profile
-
Send Message
Posted Aug 31, 2012@MrMime22
Wow, entitled much? Nothing is forcing you to use 1.3.2 beta, and if you don't like the pace of NoLagg's development, feel free to stop using it and use another plugin instead, or better yet write your own so we can demand you perform to our expectations... for free.
-
View User Profile
-
Send Message
Posted Aug 31, 2012-
View User Profile
-
Send Message
Posted Aug 31, 2012*Stop ingoring the people!* THIS BUG IS A COMMON BUG AND ITS CAUSING OUR SERVERS TO LOSE PLAYERS.
Link 1 of the block drop issue: http://dev.bukkit.org/server-mods/nolagg/tickets/109-block-drop-issue/
Link 2 of the block drop issue: http://dev.bukkit.org/server-mods/nolagg/tickets/82-blocks-not-dropping-items-dropped-items-disapearing/
-
View User Profile
-
Send Message
Posted Aug 31, 2012When will nolagg examine be fixed (or is it even possible in 1.3)
Please respond I loved this feature & urgently need it!
-
View User Profile
-
Send Message
Posted Aug 31, 2012I have a world holl at spawn
-
View User Profile
-
Send Message
Posted Aug 30, 2012I am using 1.3.2 and I have this chunk at x0,y0 that wont load. Please fix this. The config is default except for mob control is off. I don't have spout.
-
View User Profile
-
Send Message
Posted Aug 30, 2012lol i just spent forever removing and slowly adding my plugins back to find out why I had missing chunks.
I guess I'll add this back in when bukkit and this are both more stable
-
View User Profile
-
Send Message
Posted Aug 30, 2012java.lang.String.substring(String.java:1949) 09:27:01 PM CONSOLE: [SEVERE] at com.bergerkiller.bukkit.nolagg.NoLaggUtil.findPlugins(NoLaggUtil.java:70) 09:27:01 PM CONSOLE: [SEVERE] at com.bergerkiller.bukkit.nolagg.NoLaggUtil.findPlugins(NoLaggUtil.java:61) 09:27:01 PM CONSOLE: [SEVERE] at com.bergerkiller.bukkit.nolagg.threadlocknotifier.ThreadLockChecker.run(ThreadLockChecker.java:80) 09:27:01 PM CONSOLE: [SEVERE] at com.bergerkiller.bukkit.common.AsyncTask$1.run(AsyncTask.java:20) 09:27:07 PM CONSOLE: [INFO] Read timed out 09:27:09 PM CONSOLE:
-
View User Profile
-
Send Message
Posted Aug 30, 20121.88.1 finally seems to work again *yey*
No more missing chunks, everything seems fine. Maybe some small issue with the stacking (user not being able to pick up?!), but we're still investigating - nothing too big though.
THX a lot for keeping up your work!
-
View User Profile
-
Send Message
Posted Aug 30, 2012@bergerkiller
will keep that in mind. have tested the ssd and found it to be in good working order. noticed much better performance after moving from hawkeye to logblock. i know hawkeye is known for excessive read/write operations to sql so maybe that was tying up the bus or something.