The queue, by account
One shared queue. Each account advances by the nodes it already has queued, so the first request of a newcomer is served before the thousandth of a heavy user, and a big batch interleaves instead of walling the queue. Running a worker gives exactly one scheduling advantage: while it runs, it serves its owner's requests first.
| Account | Waiting | Running | Queued nodes | Served (60 min) | Oldest wait |
|---|---|---|---|---|---|
| randomchampgamer | 2511 | 2 | 321.66B | 50.34B (27.5%) | 19 hours |
| StealYourKidney2 | 406 | 1 | 248.08B | 10.00B (5.5%) | 8 hours |
| auranvesdranor | 168 | 3 | 21.89B | 79.12B (43.2%) | 15 minutes |
| Anonymous | 24 | 0 | 3.07B | 0 (0.0%) | 11 hours |
| BManBJ | 3 | 4 | 896.0M | 33.47B (18.3%) | just now |
| NeoArcturus | 0 | 1 | 512.0M | 9.73B (5.3%) | |
| Sircachetes | 0 | 0 | 0 | 384.0M (0.2%) |
Served counts the nodes the fleet actually spent in the last 60 minutes, not what was asked for. An account with nothing waiting still appears while it has recent deliveries to account for.