VoxelBench 2.0.2

Fast machines get their score again

A patch release with a single fix: on a fast machine, a benchmark could come back without any score. Everything else is identical to 2.0.1.

What was wrong

Every test sets aside its first seconds of TPS measurement: one second for the monitor to settle, then five seconds of warm-up. The warm-up exists for the gameplay tests, which build their zones and spawn thousands of entities before the real measurement starts — leaving that out is part of what keeps results steady from one run to the next.

The hardware, CPU and network tests prepare nothing in the world, yet they waited out the same six seconds. And the multi-core test does a fixed amount of work, so it ends sooner on a faster machine: on an 18-core server it finished in 6.0 seconds, before the first TPS sample was taken. The test was reported as unmeasured, and no score was computed for the whole report.

What changed

Tests whose load does not run in the world — disk, memory, multi-core, network — now measure from their second second. Gameplay tests keep their warm-up, and the single-core and world-save tests were already timing their own start.

Scores are unchanged. Throughput results such as operations per second or MB/s do not depend on that window; only the TPS figures reported alongside those tests now include seconds 2 to 5, with the main thread idle.

Upgrade

Drop the new jar in plugins/ and restart. No config or data migration.