Arthur Marsh wrote on 12/05/17 23:09:
It does seem to be related to chromium starting up several processes when opening extra windows/tabs.
I tried using ionice -c3 on chromium, which meant that disk I/O by chromium should only occur when disk I/O was otherwise idle, and this made a major difference.
It appears that chromium's use of multiple processes and threads means that it effectively hogs all the disk I/O but ends up not being able to do much as different processes/threads are making different demands on disk I/O, leading to kswapd0 having the greatest CPU usage of any process but still under 1 percent of available CPU time and the system spending over 99 percent of the time in wait. All while about 1 GiB of 4 GiB available swap is being used.
Is there any existing way to limit the chromium process tree to have the same amount of access to disk I/O as say firefox running as a single process?
Arthur. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
