Hello,

We have to pre-render custom map with OTG and fill command. Problem is that we use last spigot, otg for 1.12 and it's clear install on server with 32 cpu's every to 3,7GhZ, 64gb ddr4, 500GB SSD with very fast access. So hardware and software is i think fine.

After changing server 2 times and trying many combinations with /wb fill 100-10000 0 false we got usually that.

As you see it's almost impossible to render map that have only 16k x 16k. We are doing it from 3 days with that result at this moment. I never had that problem with fill by years.

Yeah, strange. Clearly you have plenty of memory, which would have been one of the two things I'd think most likely to cause the sort of problem. The other thing would be setting too high of a frequency on the Fill command. Since you mention trying 100-10000 for the frequency, you might try the default frequency of 20 to see if that helps. As powerful as your server is, I kind of doubt it in your case, but overly high frequencies can actually un-intuitively cause that sort of slowdown instead of improving the speed.

One other thought, you are using version 1.8.7 of the plugin since you're on 1.12, right?

Cpu's can have 3,7 on HT normally start from 2,5. Yea that's right i'm on 1.8.7 with final build of spigot for last 1.12. I tried to use Paper as well.

Started will defaults 20 at start it's fine about 100, but after 5 minutes it's drop to like 20-30 and after next couple minutes values <10 starts to show.

Do you have any other plugins running which make changes to world generation? Those could cause the process to take longer. Or do you have a mapping plugin like DynMap running? If so, you might consider disabling map updates temporarily for it until the process is complete, and do a fullrender after the world is generated.

One other thing I can think of which you might try would be to set a higher value (or possibly 0) for the fillautosave option to see if that helps.

/wb fillautosave [seconds] - set the interval for automatic saving of the world during the Fill process. Default 30 seconds, set to 0 to disable automatic world saving (not recommended).
Permission: worldborder.fillautosave

Dynmap was tested to but for now i disabled it at all and tried fillauto. With 0 it's helps a little bit, but still i have to restart server time to time.

Maybe setting the max memory to a lower value might help. If max memory is very high, many chunks can be kept loaded which can slow down the server.

In my experience WB has started eating RAM very aggressively. It dosnt matter how much mem I allocate - always getting
Available memory is very low, task is pausing. A cleanup will be attempted now, and the task will automatically continue if/when sufficient memory is freed up. Alternatively, if you restart the server, this task will automatically continue once the server is back up.

Also, thank you for hint with chunksPerRun value - I reduced it to 1 and the process became faster.

Hi - I'm having this issue on Paper build 167 for Minecraft 1.14.4, using WB 1.9.10 beta. I was getting issues running out of memory, but disabling dynmap while I generate chunks seems to fix that. But it is going very slowly:

@DmitryRendov what is the chunksPerRun value you mention?

Edit: disabling dynmap didn't stop it from running out of memory, but it's definitely better. It seems to run out at around 2.5gb free memory (I'm allowing 4GB)