linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	Alkis Georgopoulos <alkisg@gmail.com>
Cc: linux-mm@kvack.org, bugzilla-daemon@bugzilla.kernel.org,
	Mel Gorman <mgorman@techsingularity.net>,
	Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [Bug 196157] New: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x
Date: Fri, 23 Jun 2017 09:13:24 +0200	[thread overview]
Message-ID: <20170623071324.GD5308@dhcp22.suse.cz> (raw)
In-Reply-To: <20170622123736.1d80f1318eac41cd661b7757@linux-foundation.org>

On Thu 22-06-17 12:37:36, Andrew Morton wrote:
[...]
> > Me and a lot of other users have an issue where disk writes start fast (e.g.
> > 200 MB/sec), but after intensive disk usage, they end up 100+ times slower
> > (e.g. 2 MB/sec), and never get fast again until we run "echo 3 >
> > /proc/sys/vm/drop_caches".

What is your dirty limit configuration. Is your highmem dirtyable
(highmem_is_dirtyable)?

> > This issue happens on systems with any 4.x kernel, i386 arch, 16+ GB RAM.
> > It doesn't happen if we use 3.x kernels (i.e. it's a regression) or any 64bit
> > kernels (i.e. it only affects i386).

I remember we've had some changes in the way how the dirty memory is
throttled and 32b would be more sensitive to those changes. Anyway, I
would _strongly_ discourage you from using 32b kernels with that much of
memory. You are going to hit walls constantly and many of those issues
will be inherent. Some of them less so but rather non-trivial to fix
without regressing somewhere else. You can tune your system somehow but
this will be fragile no mater what.

Sorry to say that but 32b systems with tons of memory are far from
priority of most mm people. Just use 64b kernel. There are more pressing
problems to deal with.
-- 
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>

  parent reply	other threads:[~2017-06-23  7:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-196157-27@https.bugzilla.kernel.org/>
2017-06-22 19:37 ` [Bug 196157] New: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x Andrew Morton
2017-06-22 20:58   ` Alkis Georgopoulos
2017-06-23  7:13   ` Michal Hocko [this message]
2017-06-23  7:44     ` Alkis Georgopoulos
2017-06-23 11:38       ` Michal Hocko
2017-06-26  5:28         ` Alkis Georgopoulos
2017-06-26  5:46           ` Michal Hocko
2017-06-26  7:02             ` Alkis Georgopoulos
2017-06-26  9:12               ` Michal Hocko
2017-06-29  6:14                 ` Alkis Georgopoulos
2017-06-29  7:16                   ` Michal Hocko
2017-06-29  8:02                     ` Alkis Georgopoulos
2018-04-19 20:36                       ` Andrew Morton
     [not found] <234273956.1792577.1524210929280.ref@mail.yahoo.com>
2018-04-20  7:55 ` Thierry
     [not found] <328204943.8183321.1534496501208.ref@mail.yahoo.com>
2018-08-17  9:01 ` Thierry
2018-08-17  9:29   ` Michal Hocko
     [not found] <1978465524.8206495.1534505385491.ref@mail.yahoo.com>
2018-08-17 11:29 ` Thierry
2018-08-17 14:46   ` 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=20170623071324.GD5308@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alkisg@gmail.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    /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;
as well as URLs for NNTP newsgroup(s).