Paper has one main tick thread. Loom shares the work.
Loom is a multithreaded Minecraft server built on Paper that runs world work in parallel instead of on a single tick thread. Simple Servers writes Loom and hosts it — it installs from the panel's software list on any plan, from $4 a month. It is designed for Bukkit and Paper plugin compatibility; test your own plugin set before moving a live server.
A tick is 50 ms. Both are over it — this load is meant to hurt. Paper is 6.9 ticks behind; Loom is 3.1.
2.2×lower tick time on four cores342.78 ms → 152.98 ms
5.0×lower tick time on twelve325.84 ms → 64.55 ms
1.35cores Paper uses, either way134% and 141% measured
Benchmark
Is Loom faster than Paper?
In this entity-heavy test, yes. We used the same cloned world, 24 players across the overworld, nether and end, 300 entities per region, and Java 25 — Paper 26.1.2 against Loom on the same Minecraft version. Three trials each, running order alternated, median shown. Other workloads can behave differently.
Four vCPUs
Capped benchmark run
Server pinned to vCPUs 0–3 with four Loom region threads; load generators isolated on 4–11. Standard hosting plans are not core-pinned.
Paper343ms
Loom153ms
Worst TPS
3→7
p99 tick
359ms→174ms
CPU used
134%→392%
Twelve vCPUs
Uncapped benchmark run
Same world template, load and Java version; Loom used six region threads in this run, versus four in the capped run.
Paper326ms
Loom65ms
Worst TPS
3→15
p99 tick
353ms→96ms
CPU used
141%→900%
Between those two setups Loom used 2.30× the CPU and its tick time fell by 2.37×. The uncapped run also used six Loom region threads instead of four. This comparison shows how the configured setups performed; it does not isolate core count as the only cause. Paper drew 134% and 141% in the two runs.
What this test is not
A deliberate overload. Both servers sit below 20 TPS — the point is that a load which drops Paper to 3 TPS leaves Loom at 7 on four cores and 15 on twelve. It is one entity-heavy scenario at one player count, against a development build of Loom. A server without spare CPU capacity may see little benefit. These are our own measurements, and the raw run files for this comparison are not public yet. Treat the figures as a vendor-run test, not independent evidence.
What it is
What is Loom?
Loom is a multithreaded Minecraft server built on Paper. It runs world work in parallel while keeping mutable state inside the domain responsible for it, and routes each operation through a safe execution path rather than assuming everything happens on one thread. Ordinary plugins can work without modification, but a live server should test its own plugin set.
It is written by Simple Servers' co-founder and released under the GPLv3. You do not have to host with us to run it.
Built on Paper for Bukkit and Paper plugin compatibility; test your plugin set
World work runs in parallel; mutable state stays inside the domain that owns it
Per-version builds — a jar built for one Minecraft version will not run another
Java 25 or newer
GPLv3, developed in the open
Which plan should a Loom server use?
Loom can use spare CPU capacity on workloads it can parallelise. Diamond's four vCPU limit is the smaller configuration in our test above. Test your own server before choosing a larger plan for Loom alone.