Fast with a big world, and we show the numbers
Many writing tools slow down once a world gets big. We test LoreHub with thousands of articles and hundreds of dialogues, and publish exactly what we measure.
The test world
The size of a long RPG, built from scratch for every run through the same API the app uses.
How long each screen takes
Server time for everything a screen loads. Typical is the median run; slowest is the 95th percentile.
| Screen or action | Typical | Slowest | Data |
|---|---|---|---|
| Open the world (loads every article) | 38 ms | 87 ms | 645 KB |
| Open a story (dialogue list) | 90 ms | 108 ms | 46 KB |
| Open a 1,000-node dialogue | 50 ms | 242 ms | 1,103 KB |
| Search the whole world | 16 ms | 25 ms | — |
| Save a change on the canvas | 14 ms | 16 ms | — |
| Export a 1,000-node dialogue to JSON | 4,040 ms | 4,177 ms | 1,555 KB |
Measured on October 24, 2026, 30 timed runs per screen.
How we measure
The benchmark is a script in our repository, so anyone on the team can run it and get the same world.
Each run starts the LoreHub API and SQL Server from scratch on a clean machine, then builds the test world.
The first few loads of each screen are skipped, then every load after that is timed and counted.
Each screen sends the same requests in parallel that the app sends. Your own network and browser come on top of these numbers.
We run the benchmark again when we change how LoreHub loads or saves data, and update this page.
Live status
See right now whether the app, the API and the services behind them are working.