1

What are useful rule-of-thumbs with regard to interpreting non-zero vmstat "bi/bo" values? When are the values "okay" and when are they an indication of that the system is under heavy stress?

The question is of course hard to answer in the general case, but I'm looking for rule of thumbs rather than exact rules.

2 Answers 2

3

It's probably a lot better to run "iostat -x" which will often give a percentage utilization of disk I/O bandwidth for each device.

If you don't have iostat, then I'd run "hdparm -t /dev/sda " in a loop for a while while running vmstat in another window to give you a baseline for what a lot of I/O looks like.

1
  • Agreed; % utilisation is often far more useful, and it's surprising how few MB/s a busy (traditional hard) disk can sustain under random workloads and/or high I/O queue lengths. Also, iotop or htop's I/O tab are great for identifying the main culprit processes.
    – screwtop
    Jan 12, 2023 at 22:42
1

bi and bo represent the data transfers between virtual memory and block devices. It depends on your workload. No rule of thumb exists.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .