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.
@XYZ24324773
Yea, there's no way I can put NoLagg back on the server until I know that it won't corrupt chunks. I was paged to login and fix the server because half the world had been replaced by odd chunks, looking like misplaced or regenerated with a different world key.
I found that even without generating any new worlds there are still some chunks getting corrupted. The difference is that there are no error messages.
Here it is. My nolagg version: 1597 R1 (don't know what version is that but should be the latest before 1.1 came out) http:pastebin.com/XTG4ArHi
@bergerkiller - Any chance of getting one of these newer "no corrupted chunks" versions back ported to CB 1.0.1 -R1 for those of us using modded servers that cannot update yet?
Updated to 1.57.9, and this is the error I got:
2012-01-17 19:15:39 [SEVERE] Error occurred while enabling NoLagg v1.57.9 (Is it up to date?): org/getspout/spout/packet/standard/MCCraftPacket java.lang.NoClassDefFoundError: org/getspout/spout/packet/standard/MCCraftPacket at com.bergerkiller.bukkit.nolagg.NoLagg.loadConfig(NoLagg.java:188) at com.bergerkiller.bukkit.nolagg.NoLagg.onEnable(NoLagg.java:109) at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:232) at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:1034) at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:252) at org.bukkit.craftbukkit.CraftServer.loadPlugin(CraftServer.java:190) at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:173) at org.bukkit.craftbukkit.CraftServer.<init>(CraftServer.java:132) at net.minecraft.server.ServerConfigurationManager.<init>(ServerConfigurationManager.java:52) at net.minecraft.server.MinecraftServer.init(MinecraftServer.java:148) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:407) at net.minecraft.server.ThreadServerApplication.run(SourceFile:465) Caused by: java.lang.ClassNotFoundException: org.getspout.spout.packet.standard.MCCraftPacket at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:41) at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:29) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) ... 12 more
Enabling Spout makes it go away.
@Gnintendo That was solved in 1.57.7 - 1.57.9 (took me 7 hours to fix it...ended up being a faulty data pool buffer...)
Also, uploaded 1.57.9, adding multi-threaded chunk packet compression (useful for ore obfuscators, as that was an issue previously). Brings tick rate impact caused by chunk sending down to 0.1-0.5 ms per tick or so. I'll add more on separate pages...
I thought you said you were aware of a glitch that could majorly corrupt worlds when the server was shutdown? Is this no longer applicable?
@Gnintendo No, but I can't speak for others. Apparently even if it is 100% stable on my server, it manages to screw up on other servers occasionally...so do make a world backup just in case.
So will 1.57.8 still corrupt my world or not?
@XYZ24324773 What version of NoLagg did you use? What were the errors? (pastebin.com/pastie.org) If you used versions lower than 1.57.7, then it is probably already fixed.
@squidicuz
@squidicuz, you using Spout? I know I had to just remove Spout build 688 due to the door/trapdoor issue. Not currently running nolagg at the moment.
-edit-
just re-enabled spout and tried right clicking rather than left clicking and yes, it allows me to open doors then. Will have to wait for a new build.
I think this plugin corrupts my map with another plugin ' Multiverse2 ' . I couldn't create skylands and console got spammed with errors mentioning nolagg. Later on, I found some chunks were messed up and filled with pieces of buildings from other places.
@bergerkiller
Would chunk corruption include doors not being able to be opened by all players? For some players, in certain chunks, they cannot use doors. But other players can use that same door. I'm not entirely sure how this happened or what is causing it, but it seems certain chunks are having slight issues with some players.
Edit: Well... nevermind. It seems the issue is that you can no longer punch open doors. Doors, buttons and levers can only be used by alt/right clicking. Maybe I missed this in release notes or something. Damn that was frustrating. This was not caused by NoLagg or any other plugins it seems.
NoLagg seems to be running fine for me, Craftbukkit 1744
@bergerkiller While trying to diagnose an issue on my server where one core jumps to 100% 10 seconds after server start, I found it's caused by NoLagg.
I have NoLagg's chunkUnloadDelay set to 10000, the same time as when I notice the processing time jump.
Using BukkitInsider, I found this only 30 seconds after the server started, with no one connected:
Looks like NoLagg is calling CHUNK_UNLOAD on every single existing chunk when it first starts. I have a pretty big server, so it looks like it's asking to unload all 324,000 chunks after that first 10 seconds after bootup.
Should we use NoLagg and Ptweaks together? I read somewhere that nolagg is better with cpu, and ptweaks is better for ram.
Uploaded versions 1.57.7 and 1.57.8. Both are the same plugin, but 1.57.8 is for CB#1769 and 1.57.7 for CB#1744.
I added support for the Spout version of 'ore to client obfuscation'. It will obfuscate chunks before sending them, but this will cause a tick rate loss at some point.
Note: using NoLagg you can now use Ore to client obfuscation on CB#1769. To do this, you can remove Spout if this is bugging you, it will detect it nevertheless.
Are any versions safe to use with 1.1?
Ill use 1.54.8 for now then, hope you fix it soon, 1.56 looks great besides those issues.
@FireFreak111 Nope, unfortunately not. I am still heavily debugging a lot of things. Right now I fixed 2/3 chunk corruption causes..the final one is when the server is stopped. For some reason it then hustles all chunks around...reaallly bad.
So is 1.56.8 fully fixed and stable? My servers lagging alot on an i7-860 and a 6850 card, 8gb ddr3 and a 1-5mb/s connection. Harddrive is sata, 7200rpm. No clue whats causing it, would like to test nolagg again, but does that build have chunk corruption issues.
@Giinger Not caused by NoLagg, thrown by NoLagg. Report this error to the author of MyWarp (taylorkelly), he is teleporting from another thread.