/wb fill very slow on 1.14.4

[willc5]

Only 1% of the world generated overnight at default fill command. How can I make it faster? No point in pregenerating if it's gonna take a month

At this moment it's generating 10-20 chunks per second

[willc5]

And can I change the fill frequency while it's running or paused

[FrostDelta123]

Same. Paper-spigot 1.14.4. 30x30k map. 40% by 7 days 20GB RAM doesnt help. screen http://prntscr.com/owiyzl

[Tsoccerguy3]

you must run this switch at least 1 time --forceUpgrade server argument

Upgrading Although upgrades from between any two version pairs are technically possible, it is recommended that all upgrades are conducted from 1.13.2. This means that you should first upgrade your world completely on 1.13.2 using the --forceUpgrade server argument, and then do the same on 1.14.

[BoomEaro]

I confirm, the world is being generated too slowly. The interesting thing is that if you stop generating the world and start it again, then the plugin will quickly generate chunks for some time. However, then it will again generate slowly. Moreover, at these moments, the load on the CPU is very high.

[Tsoccerguy3]

do /timings report , to see if there is a mem leak or a bad plugin

[mxs42]

@BoomEaro it doesn't generate quickly on start, it just doesn't regenerate what already was generated. It skips sectors and then starts generating normally, I think this is can not be fixed because world generation is slow in general in 1.14.

[dylantknguyen]

Seems to be a memory leak in the newer version of Spigot 1.14.4. After reverting back to this release of Paper-1.14.4, the problem seemed to be gone. I plan to let it generate for the next few days before switching back to my normal jar.

Edit: I was using paper-176 before.

[ShiftingKill]

Can anyone confirm if leaving a player AFK somewhere helps this issue? Just noticing now that the hundreds/sec and thousands/sec are more frequent with an AFK admin on. Noticeable enough to not want to restart every 10 minutes. @FrostDelta123 I also am around that same setup but mine is 20k circular radius and its a 1/3 of the way done in 2 days.

[Puremin0rez]

I honestly think there's either a memory leak in WorldBorder or a memory leak in the chunk loading system somewhere.

I'm generating a 50k x 50k (25k each direction) border and while I do realize this will take days to complete, I've had to resort to setting up a cron job to restarting the server hourly to recover the memory that is seemingly being permanently eaten. The chunk generation starts off quick enough (100-120~ chunks) and then drops quite drastically as the memory starts to get lower (10-30~ chunks) and will complain about freeing up memory quite often. This is with 20GB allocated.

[a3s]

For future readers: use chunkmaster. WorldBorder is buggy and I don't see how it can be useful nowadays. Chunkmaster works fast and without any issues, world border is a vanilla future now.

tldr: do not use WorldBorder plugin