search

Azanor / thaumcraft-5

localization and bug reporting
55 stars 46 forks source link

Auras taking x ms longer than normal #614

Open ghost opened 8 years ago

ghost commented 8 years ago

[20:56:21] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 435 ms LONGER THAN NORMAL [20:56:23] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 518 ms LONGER THAN NORMAL [20:56:26] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 427 ms LONGER THAN NORMAL [20:56:31] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 1712 ms LONGER THAN NORMAL [20:56:34] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 918 ms LONGER THAN NORMAL [20:56:37] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 577 ms LONGER THAN NORMAL [20:56:40] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 540 ms LONGER THAN NORMAL [20:56:43] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 416 ms LONGER THAN NORMAL [20:56:45] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 409 ms LONGER THAN NORMAL [20:56:49] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 1347 ms LONGER THAN NORMAL [20:56:52] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 413 ms LONGER THAN NORMAL [20:56:56] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 408 ms LONGER THAN NORMAL [20:57:00] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 696 ms LONGER THAN NORMAL [20:57:03] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 722 ms LONGER THAN NORMAL [20:57:07] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 398 ms LONGER THAN NORMAL [20:57:09] [Thread-15/WARN] [THAUMCRAFT]: AURAS TAKING 416 ms LONGER THAN NORMAL

The aura queue just keep spamming my console log with this message every 2-4 seconds. I'm not really sure why its happening. I tried it with just Thaumcraft as well, the message still displays and lags the server.

MC: 1.8.9 Forge: forge-1.8.9-11.15.1.1902-1.8.9-universal

bunSakurAing commented 8 years ago

I have the same problem. log：http://pastebin.com/49fbGNzG

This problem not only lag server also cause player connection timeout, I hope this problem can be settled as soon as possible

chrisbecke commented 7 years ago

If you get this error you are not running your server with the correct garbage collection parameters. The default command line always includes -XX:+UseConcMarkSweepGC and -XX:+UseParNewGC for a reason. Ensure that you launch java with them

Jotolink commented 7 years ago

-XX:+UseConcMarkSweepGC and -XX:+UseParNewGC "Delete the "and" from the middle when you input that into your java argument command line...

Edit: Use care though, I just used it in a local LAN world with my wife connecting to my world and she lost everything items and data ....even her uploaded skin and went back into default Alex skin.... I still had every thing so I assume that the command being related to garbage collection might have dumped everything before its enable. and still not helping my situation with the auras lagging/slowing up the world.

chrisbecke commented 7 years ago

Garbage collection does not work like that. If it ever collected anything it shouldn't then the game would simply crash. What you describe is the kind of problem caused by people renaming their characters, or playing "offline". Especially as her skin reset.

Jotolink commented 7 years ago

Well I found out that it was an offline problem. after researching the mark and sweep seq. found out what you said about crashing was true....it was something I did, and I thought it was related to my trash bin and another compile that I thought was related.

afterwards I had to recover my wife's player dat file and information for the world ....soo lol yea that's why I thought it was a problem with that command and why I thought it was related to trash. (assuming it as i haven't come across that a garbage collection parameter problem ever.) We also didn't rename characters or anything as well, and did do a skin reset...but only after, and like you said was an offline problem. Still having problems with the auras and slowing/simulated lag. even with the command in java.

Is there any way I could paste the log file here?

also if I haven't said im using : MC: 1.8.9 Forge: 1.8.9-forge1.8.9-11.15.1.1902-1.8.9

Jotolink commented 7 years ago

Never mind found a solution... was watching a java vid on young generation. all the objects it represents for the short term of life it has during its generation, after they pass into their specific location in the heap (where that garbage collector passes ) all the new objects are renamed into "eden" after it survives it gets gc cleaned and swaps as an old gen after they survive the cleaning. I found out something on the permanent gen too where the class files are kept. all the compiled classes and jsp pages are there, if it fills then the full garbage collection gets triggered. if the FGC cant clean out old unreferenced classes and there isn't any room left to expand the perm space the out of memory error is thrown and will result in a crash which I had experienced. I hope this helps anyone else having this problem.

This is all in my jvm arguments portion of the launch options in the minecraft launcher

-Xmx2G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M -Xms1G -XX:MaxPermSize=512M

You can reduce the -XX:MaxPermSize=256M