Recent Discussions
[spark-asyncsampler-worker-thread/WARN] Timed out waiting for world statistics
Unanswered
Boxer posted this in #questions
619 messages
0 views
BoxerOP
Whenever a player joins my server they seem to always cause a massive lag spike with a chance of disconnecting all players, yall have any idea what could be causing this?
BoxerOP
@Boxer Whenever a player joins my server they seem to always cause a massive lag spike with a chance of disconnecting all players, yall have any idea what could be causing this?
Do what the second bullet point of the Admincraft Meta bot says.
@Boxer Whenever a player joins my server they seem to always cause a massive lag spike with a chance of disconnecting all players, yall have any idea what could be causing this?
that typically means your server froze and is crashing
it’s hard to come back from those
it’s hard to come back from those
@Tamz that typically means your server froze and is crashing
it’s hard to come back from those
it’s hard to come back from those
BoxerOP
It never fully crashes though, i have the timeout timers at like 3 minutes
its always accompanied by really slow chunk loading
holy SHIT dude.
image.png
BoxerOP
I think so, atleast the same type stall, or a similar
that is WAYYYY too much allocated memory
BoxerOP
we were getting OOM issues
@Boxer we were getting OOM issues
THAT is not how you solve those
BoxerOP
😂
we do about 20-30 players average
and theres lot of really unoptimized mods
OOM issues arise from exactly one situation and one situation only:
You allocate different amounts of memory to -Xms and -Xmx, the JVM reserves the -Xms amount, and then tries to grow the heap to the -Xmx value and can't, because something else reserved it first.
That is the ONLY way to get OOM crashes. Increasing allocation to 31 gigs as you have done:
1. doesn't solve that issue
2. causes lag issues
The actual reason that your OOM issues stopped is because -Xms and -Xmx are equal now, and I'm willing to bet they weren't before when you were getting your OOM issues.
You allocate different amounts of memory to -Xms and -Xmx, the JVM reserves the -Xms amount, and then tries to grow the heap to the -Xmx value and can't, because something else reserved it first.
That is the ONLY way to get OOM crashes. Increasing allocation to 31 gigs as you have done:
1. doesn't solve that issue
2. causes lag issues
The actual reason that your OOM issues stopped is because -Xms and -Xmx are equal now, and I'm willing to bet they weren't before when you were getting your OOM issues.
BoxerOP
We had OOM issues before even with our values set the same
So, you're saying to reduce the RAM even still?
Then it's offheap memory trying to grow. That can happen too.
@Boxer So, you're saying to reduce the RAM even still?
G1GC should never be used with that much memory. 99.9% of servers do not need to go above 16GB, and 95% don't need more than 12GB, even with heavy modpacks.
Loading...
Loading...