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, and your existing Bukkit and Paper plugins keep working.
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?
Yes, and the size of the difference is the number of cores you give it. Same cloned world, 24 players across the overworld, nether and end, 300 entities per region, Java 25 — Paper 26.1.2 against Loom on the same Minecraft version. Three trials each, running order alternated, median shown.
Four cores
What a Diamond plan gives a server
Server pinned to CPUs 0–3, load generators isolated on 4–11.
Paper343ms
Loom153ms
Worst TPS
3→7
p99 tick
359ms→174ms
CPU used
134%→392%
Twelve cores
The same world with the cores uncapped
Identical world, load and Java version; only the core count differs.
Paper326ms
Loom65ms
Worst TPS
3→15
p99 tick
353ms→96ms
CPU used
141%→900%
Between those two runs Loom used 2.30× the CPU and returned 2.37× the tick reduction. It scales with the cores it is given. Paper drew 134% and 141% in the same two tests, because a single tick thread cannot spend cores it is offered.
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. On a server with no spare cores you will see no difference at all, because there is nothing for Loom to parallelise into. Raw tick data, config hashes and jar checksums for both runs are published with the source.
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 — which is why ordinary plugins keep working.
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, so Bukkit and Paper plugins run unchanged
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 turns cores into tick headroom, so it rewards the larger plans: Diamond's four cores are where the difference above begins. Heavier plans are coming for servers that want more of it.