Open garrettjoecox opened 2 years ago
Just to make sure, are you basing anything on yesterday's aws outage? Anything weird that happened yesterday would likely be related to that.
Na, that definitely did give me some down time, but this was before and after downtime yesterday. It’s not unplayable, but it’s definitely noticeable
Looks like it might have been a bug in 1.18 rc1, going to try out 1.18 rc2 tonight
Edit: Still having poor performance
@garrettjoecox it's also possible that your filesystem's burst credits have accumulated now over time. When I first launched EFS was indeed slow, but now chunk loading is pretty quick!
@Stealthii How long did it take your your loading to speed up? Was there any other issues like low TPS/lag before that happened?
@cggentry115 I tell a lie - it seems I was relaying performance of a running server that had clearly cached some loading. On any new task running, heading to/from Nether into unloaded chunks really shows the slow performance (about 8 seconds to load all chunks before transition)
Perhaps someone more familiar with the tools being used could try something like:
before the server starts up, copy the world directory to the local filesystem Spin up the server with the world on the local filesystem On server close, overwrite world directory on mounted EFS with the newer copy in the local filesystem.
This might help verify if it is indeed an EFS issue
With the above setup you'd likely be able to ditch EFS all-together and use S3 instead...
I've been tweaking a number of parameters including minecraft version, java flags, data packs, and server specs. All seem to perform worse than what I'm used to for similar server specs in terms of chunk loading (both new and old chunks). I'm wondering if anyone else is experiencing this issue, and if it could perhaps be EFS at fault.