If R (runqueue) is greater in B (waitqueue) in vmstat, is is I/O bound?
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
If the runqueue is the number of processes waiting for their turn on the CPU + processes currently running, and waitqueue is the number of processes waiting for I/O, then wouldnâÂÂt B in the vmstat output being greater than R mean that there is an I/O bound, not CPU bound? I am confused because the link below says the opposite ...
From http://nonfunctionaltestingtools.blogspot.com/2013/03/vmstat-output-explained.html?m=1
âÂÂIf runnable threads (r) divided by the number of CPU is greater than one -> possible CPU bottleneck (The (r) coulmn should be compared with number of CPUs (logical CPUs as in uptime) if we have enough CPUs or we have more threads.) High numbers in the blocked processes column (b) indicates slow disks. (r) should always be higher than (b); if it is not, it usually means you have a CPU bottleneckâÂÂ
cpu-usage
New contributor
add a comment |Â
up vote
1
down vote
favorite
If the runqueue is the number of processes waiting for their turn on the CPU + processes currently running, and waitqueue is the number of processes waiting for I/O, then wouldnâÂÂt B in the vmstat output being greater than R mean that there is an I/O bound, not CPU bound? I am confused because the link below says the opposite ...
From http://nonfunctionaltestingtools.blogspot.com/2013/03/vmstat-output-explained.html?m=1
âÂÂIf runnable threads (r) divided by the number of CPU is greater than one -> possible CPU bottleneck (The (r) coulmn should be compared with number of CPUs (logical CPUs as in uptime) if we have enough CPUs or we have more threads.) High numbers in the blocked processes column (b) indicates slow disks. (r) should always be higher than (b); if it is not, it usually means you have a CPU bottleneckâÂÂ
cpu-usage
New contributor
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
If the runqueue is the number of processes waiting for their turn on the CPU + processes currently running, and waitqueue is the number of processes waiting for I/O, then wouldnâÂÂt B in the vmstat output being greater than R mean that there is an I/O bound, not CPU bound? I am confused because the link below says the opposite ...
From http://nonfunctionaltestingtools.blogspot.com/2013/03/vmstat-output-explained.html?m=1
âÂÂIf runnable threads (r) divided by the number of CPU is greater than one -> possible CPU bottleneck (The (r) coulmn should be compared with number of CPUs (logical CPUs as in uptime) if we have enough CPUs or we have more threads.) High numbers in the blocked processes column (b) indicates slow disks. (r) should always be higher than (b); if it is not, it usually means you have a CPU bottleneckâÂÂ
cpu-usage
New contributor
If the runqueue is the number of processes waiting for their turn on the CPU + processes currently running, and waitqueue is the number of processes waiting for I/O, then wouldnâÂÂt B in the vmstat output being greater than R mean that there is an I/O bound, not CPU bound? I am confused because the link below says the opposite ...
From http://nonfunctionaltestingtools.blogspot.com/2013/03/vmstat-output-explained.html?m=1
âÂÂIf runnable threads (r) divided by the number of CPU is greater than one -> possible CPU bottleneck (The (r) coulmn should be compared with number of CPUs (logical CPUs as in uptime) if we have enough CPUs or we have more threads.) High numbers in the blocked processes column (b) indicates slow disks. (r) should always be higher than (b); if it is not, it usually means you have a CPU bottleneckâÂÂ
cpu-usage
cpu-usage
New contributor
New contributor
New contributor
asked 3 hours ago
John Alvarez
61
61
New contributor
New contributor
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
A higher number in b
than in r
means the CPUs are often idle, so you are right being confused. The document should have read 'means you have an I/O bottleneck'.
Beware that is says r
should never be higher than the number of CPUs, and r=16 on a 12 CPU system is a "serious" problem. This is quite exaggerated. That just means CPUs are fully used and some threads are waiting. Usually no big deal.
Finally, don't confuse threads and processes, like the linked document sometimes does too. The r
and b
columns show number of threads, not processes. Not all processes are single threaded.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
A higher number in b
than in r
means the CPUs are often idle, so you are right being confused. The document should have read 'means you have an I/O bottleneck'.
Beware that is says r
should never be higher than the number of CPUs, and r=16 on a 12 CPU system is a "serious" problem. This is quite exaggerated. That just means CPUs are fully used and some threads are waiting. Usually no big deal.
Finally, don't confuse threads and processes, like the linked document sometimes does too. The r
and b
columns show number of threads, not processes. Not all processes are single threaded.
add a comment |Â
up vote
2
down vote
A higher number in b
than in r
means the CPUs are often idle, so you are right being confused. The document should have read 'means you have an I/O bottleneck'.
Beware that is says r
should never be higher than the number of CPUs, and r=16 on a 12 CPU system is a "serious" problem. This is quite exaggerated. That just means CPUs are fully used and some threads are waiting. Usually no big deal.
Finally, don't confuse threads and processes, like the linked document sometimes does too. The r
and b
columns show number of threads, not processes. Not all processes are single threaded.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
A higher number in b
than in r
means the CPUs are often idle, so you are right being confused. The document should have read 'means you have an I/O bottleneck'.
Beware that is says r
should never be higher than the number of CPUs, and r=16 on a 12 CPU system is a "serious" problem. This is quite exaggerated. That just means CPUs are fully used and some threads are waiting. Usually no big deal.
Finally, don't confuse threads and processes, like the linked document sometimes does too. The r
and b
columns show number of threads, not processes. Not all processes are single threaded.
A higher number in b
than in r
means the CPUs are often idle, so you are right being confused. The document should have read 'means you have an I/O bottleneck'.
Beware that is says r
should never be higher than the number of CPUs, and r=16 on a 12 CPU system is a "serious" problem. This is quite exaggerated. That just means CPUs are fully used and some threads are waiting. Usually no big deal.
Finally, don't confuse threads and processes, like the linked document sometimes does too. The r
and b
columns show number of threads, not processes. Not all processes are single threaded.
answered 2 hours ago
jlliagre
45.4k680129
45.4k680129
add a comment |Â
add a comment |Â
John Alvarez is a new contributor. Be nice, and check out our Code of Conduct.
John Alvarez is a new contributor. Be nice, and check out our Code of Conduct.
John Alvarez is a new contributor. Be nice, and check out our Code of Conduct.
John Alvarez is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f475351%2fif-r-runqueue-is-greater-in-b-waitqueue-in-vmstat-is-is-i-o-bound%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password