IO and IOPS: disk activity limits

Alongside CPU and memory, DirhamGuard manages how much disk activity your account generates. This is measured in two ways:

• IO (input/output) - the speed of data moving to and from the disk, like litres per minute through a pipe.
• IOPS (input/output operations per second) - the number of separate read or write actions per second, like the number of individual sips rather than the total volume.

Every time your site reads a file, writes to a log, or queries a database, it uses a little IO. Most sites barely register. Heavy IO usually comes from a few specific culprits:

• Large or frequent backups running during peak hours.
• Log files that grow out of control (often from an error being repeated thousands of times).
• Plugins that write to disk on every page load, or a database that is not indexed well.
• Bulk imports and exports of large files.

If you hit your IO or IOPS ceiling, disk-heavy tasks slow down until activity settles - your site stays online but may feel sluggish during the spike.

To reduce disk activity: schedule backups for quiet hours, clear or rotate large log files, remove plugins that log excessively, and use caching so pages are served from memory rather than rebuilt from disk each time. You can review IO usage in the DirhamHost panel. If a graph looks unusual and you cannot find the cause, our UAE team can investigate with you at support@dirhamaday.ae.