Performance

Performance

All numbers are measurements on the hardware and scene below – not a promise for other computers, modpacks or worlds.

Hardware

Laptop with an Intel Core i7-13700H, 32 GB RAM, Intel Iris Xe graphics, Windows 11. Java 21 (Minecraft 1.21.1) and Java 25 (26.3). Measured on the two ends of the version range, 1.21.1 and 26.3, both loaders; the versions between share the same game code.

Server

A dedicated server with a large build: 12 running plants (2 Foundries, 2 Chemical Plants with 4 columns, 2 Assembly Complexes with 5 stations, 2 Agricultural Facilities at ×8, a Particle Facility, a Quantum Facility with its field up, a Matter Reconstructor, a Deep Core), 96 single machines (half of them with 2 Speed and 2 Parallel Upgrades) and 8 field machines – all supplied and working. Three runs of 3 minutes each after a minute of warm-up.

Time QuantaWorks takes per server tick (a tick has 50 ms):

Minecraft	Loader	median	99th percentile
1.21.1	Fabric	0.20 ms	0.90 ms
1.21.1	NeoForge	0.25 ms	0.93 ms
26.3	Fabric	0.28 ms	1.21 ms
26.3	NeoForge	0.39 ms	1.27 ms

With a plant wall broken and rebuilt every second (the plants check themselves again), the 99th percentile stays at 1.3 – 1.6 ms. The most expensive single plant is the Assembly Complex at about 21 – 38 µs per tick; a single machine takes about 1 µs.

How the plants stay cheap: a plant checks its structure only when one of its blocks changes, never by scanning; field machines work one block per action and never load chunks; recipe lookups are cached per data reload.

Client

The renderers of a scene with all plants running (beam, field, matter stream, drill string, growing plants, stations) cost about 1.3 ms per frame on 26.3 and about 0.1 – 0.3 ms per frame on 1.21.1 on the Iris Xe. particleDensity, interiorEffects and flowEffects in the client configuration reduce the particles.

Large modpacks

With a simulated pack of 2,000 materials and 9,000 recipes, building the material and recipe tables took 77 ms after a data reload, a recipe lookup 0.4 µs, and sending the recipes to a joining player 2.5 MB.