Small reads on a shared disk answer much faster on servers with the new read limits: on three busy servers among the first to get them, the wait for a small read fell 93 to 97%.
A shared disk serves everyone on the server from one queue. Until now one account reading flat out, a big library scan or a full recheck, could fill that queue, and every small read behind it waited: a page in your web UI, a poster in your media server. With the update, each account on the server has its own read limit, so a heavy reader is held to its own share instead of filling the queue.
I measured it against servers that did not have it yet, over the same hours, so a quiet evening could not pass for an improvement.
How your limit is set
Every five minutes the server sets a read budget from how much it normally reads and how busy its disks are right now, and splits it between accounts. Your share follows your disk priority (your plan, your Free Bonus Disk percentage and the Disk IO priority extra if you have one) and your storage size. The limit covers reads only.
Where to see it
Open the info tab in your control panel. It shows "Disk reads for your account right now: up to N per second." When your account is reading at that rate, the tab says so, and further reads wait their turn until the disk is less busy or your reading slows.
If you need more
The Disk IO priority extra raises your share: +100 to +400 (+300 on Dragon-R), from €9.99 a month on seedboxes and from €19.99 on storage boxes. Add it with the Upgrade Options link in your control panel. A larger plan raises it too.
Is it on your server?
The read limit comes with the platform update. If the info tab shows the read line, your server has it. There is nothing to switch on.
How disk priority and the read limit fit together is on the wiki: Seedbox and Storage Box Disk Priority.
Best Regards,
Väinämöinen
Pulsed Media Support
(Sang the seas calm; now the disk queue)
Friday, November 6, 2026
