From: Rik van Riel <riel@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@techsingularity.net>,
theosib@gmail.com
Subject: Re: [Bug 107771] New: Single process tries to use more than 1/2 physical RAM, OS starts thrashing
Date: Fri, 15 Apr 2016 15:31:22 -0400 [thread overview]
Message-ID: <1460748682.25336.41.camel@redhat.com> (raw)
In-Reply-To: <20160415121549.47e404e3263c71564929884e@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 2608 bytes --]
On Fri, 2016-04-15 at 12:15 -0700, Andrew Morton wrote:
> (switched to email. Please respond via emailed reply-to-all, not via
> the
> bugzilla web interface).
>
> This is ... interesting.
First things first. What is the value of
/proc/sys/vm/zone_reclaim?
I am assuming this is a two socket system,
with two 12-core CPUs. Am I right?
> On Thu, 12 Nov 2015 18:46:35 +0000 bugzilla-
> daemon@bugzilla.kernel.org wrote:
>
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=107771
> >
> > Bug ID: 107771
> > Summary: Single process tries to use more than 1/2
> > physical
> > RAM, OS starts thrashing
> > Product: Memory Management
> > Version: 2.5
> > Kernel Version: 4.3.0-040300-generic (Ubuntu)
> > Hardware: All
> > OS: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: normal
> > Priority: P1
> > Component: Page Allocator
> > Assignee: akpm@linux-foundation.org
> > Reporter: theosib@gmail.com
> > Regression: No
> >
> > I have a 24-core (48 thread) system with 64GB of RAM.
> >
> > When I run multiple processes, I can use all of physical RAM before
> > swapping
> > starts. However, if I'm running only a *single* process, the
> > system will start
> > swapping after I've exceeded only 1/2 of available physical
> > RAM. Only after
> > swap fills does it start using more of the physical RAM.
> >
> > I can't find any ulimit settings or anything else that would cause
> > this to
> > happen intentionally.
> >
> > I had originally filed this against Ubuntu, but I'm now running a
> > more recent
> > kernel, and the problem persists, so I think it's more appropriate
> > to file
> > here. There are some logs that they had me collect, so if you want
> > to see
> > them, the are here:
> >
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513673
> >
> > I don't recall this problem happening with older kernels (whatever
> > came with
> > Ubuntu 15.04), although I may just not have noticed. By swapping
> > early, I'm
> > limited by the speed of my SSD, which is moving only about 20MB/sec
> > in each
> > direction, and that makes what I'm running take 10 times as long to
> > complete.
> >
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-04-15 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-107771-27@https.bugzilla.kernel.org/>
2016-04-15 19:15 ` [Bug 107771] New: Single process tries to use more than 1/2 physical RAM, OS starts thrashing Andrew Morton
2016-04-15 19:31 ` Rik van Riel [this message]
2016-04-17 18:53 ` Michal Hocko
2016-04-22 23:01 ` Timothy Normand Miller
2016-04-22 22:44 ` Timothy Normand Miller
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=1460748682.25336.41.camel@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=theosib@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;
as well as URLs for NNTP newsgroup(s).