From: Thomas Jarosch <thomas.jarosch@intra2net.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org
Subject: Re: Re: [Bug 64121] New: [BISECTED] "mm" performance regression updating from 3.2 to 3.3
Date: Wed, 27 Jul 2016 11:18:36 +0200 [thread overview]
Message-ID: <1650204.9z6KOJWgNh@storm> (raw)
In-Reply-To: <b3219832-110d-2b74-5ba9-694ab30589f0@suse.cz>
On Thursday, 21. July 2016 16:02:06 Vlastimil Babka wrote:
> > recently we've updated our production mail server from 3.14.69
> > to 3.14.73 and it worked fine for a few days. When the box is really
> > busy (=incoming malware via email), the I/O speed drops to crawl,
>
> I don't see anything either, might be some change e.g. under fs/ though.
> How about git bisect?
One day later I failed to trigger it, so no easy git bisect.
Yesterday another busy mail server showed the same problem during backup
creation. This time I knew about slabtop and could see that the
ext4_inode_cache occupied about 393MB of the 776MB total low memory.
Write speed was down to 25 MB/s.
"sysctl -w vm.drop_caches=3" cleared the inode cache
and the write speed was back to 300 MB/s.
It might be related to memory fragmentation of low memory due to the
inode cache, the mail server has over 1.400.000 millions files.
I suspect the problem is unrelated to 3.14.73 per se, it seems to trigger
depending how busy the machine is and the memory layout.
A 64 bit kernel (even with a 32 bit userspace) is the proper solution here.
Still that would mean to deprecate working 32 bit only boxes.
Cheers,
Thomas
--
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:[~2016-07-27 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-64121-27@https.bugzilla.kernel.org/>
2013-10-31 20:46 ` [Bug 64121] New: [BISECTED] "mm" performance regression updating from 3.2 to 3.3 Andrew Morton
2013-11-01 18:43 ` Johannes Weiner
2013-11-04 11:32 ` Thomas Jarosch
2016-07-18 22:23 ` Thomas Jarosch
2016-07-21 14:02 ` Vlastimil Babka
2016-07-27 9:18 ` Thomas Jarosch [this message]
2016-07-27 9:21 ` Re: " Thomas Jarosch
2016-07-27 16:44 ` Linus Torvalds
2016-07-29 17:00 ` Thomas Jarosch
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=1650204.9z6KOJWgNh@storm \
--to=thomas.jarosch@intra2net.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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).