From: Michal Hocko <mhocko@kernel.org>
To: Raymond Jennings <shentino@gmail.com>
Cc: Mike Rapoport <rppt@linux.vnet.ibm.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: Heavy I/O causing slow interactivity
Date: Wed, 5 Apr 2017 20:43:27 +0200 [thread overview]
Message-ID: <20170405184325.GV6035@dhcp22.suse.cz> (raw)
In-Reply-To: <CAGDaZ_o745MVD8PDeGhp0-oehUVb8+Zrm4g7uUBBZNTAPODbmQ@mail.gmail.com>
On Wed 05-04-17 11:15:44, Raymond Jennings wrote:
> I have 32GiB of memory
>
> Storage is an LVM volume group sitting on a pair of 2T western digital
> drives, one WD Green, and the other WD Blue
>
> My CPU is an i7, model 4790K.
>
> What I'd like is some way for my system to fairly share the available
> I/O bandwidth. My youtube is sensitive to latency but doesn't chew up
> a lot of throughput. My I/O heavy stuff isn't really urgent and I
> don't mind it yielding to the interactive stuff.
>
> I remember a similiar concept being tried awhile ago with a scheduler
> that "punished" processes that sucked up too much CPU and made sure
> the short sporadic event driven interactive stuff got the scraps of
> CPU when it needed them.
>
> /proc/sys/vm/dirty is set up as follows
>
> dirty_ratio 90
So you allow 90% of your 32GB to be dirty and then get throttled which
will take quite some time until it gets synced to the disk. Even with a
fast storage. I would really recommend reducing dirty_ratio (and
background ratio as well) to something much more reasonable. E.g. start
the background IO at around 400MB and hard limit at 800MB. I am pretty
sure that the stalls you are seeing are related to the IO dirty
throttling.
--
Michal Hocko
SUSE Labs
--
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-04-05 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 17:39 Raymond Jennings
2017-04-04 11:25 ` Michal Hocko
2017-04-05 12:53 ` Mike Rapoport
2017-04-05 18:15 ` Raymond Jennings
2017-04-05 18:43 ` Michal Hocko [this message]
2017-04-13 18:13 ` Raymond Jennings
2017-04-17 8:19 ` Michal Hocko
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=20170405184325.GV6035@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=shentino@gmail.com \
/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