From: Arthur Marsh <arthur.marsh@internode.on.net>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: linux-mm@kvack.org
Subject: Re: 8 Gigabytes and constantly swapping
Date: Sat, 13 May 2017 13:45:23 +0930 [thread overview]
Message-ID: <521c29b0-809d-a0fd-50ca-d3d0df325dd4@internode.on.net> (raw)
In-Reply-To: <b64f3ec1-0839-3051-d030-164625620712@internode.on.net>
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@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-05-13 4:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 8:51 Arthur Marsh
2017-05-12 10:56 ` Tetsuo Handa
2017-05-12 13:39 ` Arthur Marsh
2017-05-13 4:15 ` Arthur Marsh [this message]
2017-05-15 8:09 ` Michal Hocko
2017-05-17 1:27 ` Arthur Marsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=521c29b0-809d-a0fd-50ca-d3d0df325dd4@internode.on.net \
--to=arthur.marsh@internode.on.net \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox