Speed & performance
BerryOrders is built so your server never waits for it.
How it's light
- Orders live in memory. Every open order is kept in memory, sorted once per change. Opening
/order, turning a page or changing the sort is a list lookup, not a database query. - The database is only for changes. Placing, delivering, cancelling and collecting go to the database on its own thread, as one short transaction each. Nothing on the server thread ever waits for it.
- Order icons are built once per order version and reused for every player looking at the list, until the order changes or the "expires in" minute ticks over.
- Pages and sorts update the open window instead of opening a new one.
- Searches are cached until an order changes.
- Cross-server uses the database to decide every change and small Redis notes ("order 42 changed") to tell the other servers.
- Folia: every menu, delivery and payout runs on the player's own thread.
Measured
50 real Minecraft clients (bots) on Paper 1.21.8, a 4-core Intel Xeon 2.8 GHz, 2 GB RAM, SQLite, measured with spark. 500 orders, then every bot looping for a minute: open /order, next page, change the sort; deliver a stack to an order (search, put it in, confirm); open your orders; tab-complete /order.
| Per minute, 50 players | BerryOrders |
|---|---|
| Menu actions completed | about 3,000 (plus 1,000 tab-completes) |
| Server-thread time per action | about 5 ms, most of it Minecraft opening the window |
| Background CPU | under 1.2 s |
| Tick time, 1-minute average | 8.8–10.2 ms, no lag warnings |
| Items and money | every item delivered paid for exactly once |
Join wave: 50 players joining at once, 500 orders between them: no measurable server-thread time. Each player's orders load while they log in.
Tuning
There's nothing you need to tune. On a network with MySQL far away, keep max-pool at 3–4; each change is one short transaction, so more connections don't help.