Closed thetayloredman closed 1 month ago
not possible to predict as your system is finding chunks slower than it is rendering them, either increase the render speeds (fastrender sequence) or wait: renderaccelerateinterval: .001
tiles-rendered-at-once: 10
maxchunkspertick: 400
parallelrendercnt: 10
fullrenderplayerlimit: 0
per-tick-time-limit: 200
fullrender-min-tps: 5 (configuration.txt) here the server has 10 cores, change the parallelrenderct to the amount of cores you have. Next do /dynmap pause all, restart and finally do /dynmap pause none.
the render stats are mostly self-explanatory, the queue size consists of the chunks that are being worked on, and the ones that are in the queue, the cache hit rate is as far as I know, how much percentage of the called chunks to render is already cached, but not sure.
@JurgenKuyper What about processed/rendered/updated?
Also, how large is a tile (in blocks) normally?
@JurgenKuyper What about processed/rendered/updated?
Also, how large is a tile (in blocks) normally?
I don't know, but guess they are the amnt of tiles that apply to that state
@thetayloredman a tile is a chunk normally in size, zooms and stitching can change that
There's a lot of values here with barely any explanation:
I'm trying to predict how much longer is left in a render job that's been running for days. There's no documentation anywhere as to what any of these numbers mean and I'd like to know about each.