Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Which means it is basically useless - especially on a multicore (hyperthreaded) environment.
There are situations where it can be useful when used in conjunction with other metrics, but as a stand-alone indicator, use with care.
Here I understand that CPU wait time actually interrelated with Disk IO Time .But I am confused with the below points :
1) In top command , wait% event means overall system wait time or only disk io wait time ?
2)From above redhat site :
---------------
"So, %iowait means that from the CPU point of view, no tasks were runnable, but at least one i/o was in progress. iowait is simply a form of idle time when nothing could be scheduled. The value may or may not be useful in indicating a performance problem, but it does tell us that the system is idle and could have taken more work."
---------------
would you please clarify about the above sentence ? Does it mean , when Disk %iowait is increasing then CPU has no new tasks for execution or, schedule to execute .CPU goes to IDLE then ?
iowait is simply a form of idle time when nothing could be scheduled.
It was probably invented to help determine why a system was idle - back in the days of uni-processor systems. As I said above, it is largely pointless in multi-processor systems.
1). see the manpage.
2). the system is idle - iowait% is a time percentage when IO is outstanding. May, or may not, be related to the tasks not running.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.