From: jlnance@unity.ncsu.edu
To: linux-kernel@vger.kernel.org
Subject: Re: limit resident memory size
Date: Fri, 13 Jun 2003 06:21:39 -0400 [thread overview]
Message-ID: <20030613102139.GA769@ncsu.edu> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKOEBMDKAA.davids@webmaster.com>
On Thu, Jun 12, 2003 at 03:15:13PM -0700, David Schwartz wrote:
>
> > I would like to limit the maximum resident memory size
> > of a process within a threshold, i.e. if its virtual
> > memory footprint exceeds this threshold, it needs to
> > swap out pages *only* from within its VM space.
>
> Why? If you think this is a good way to be nice to other
> processes, you're wrong.
I have to disagree. I used to use a Digital Unix system, which had this
feature, to do software development. The program I was working on was
large, and linking it required more memory than the 128M that was installed
on the computer. All my makes ended with a 10 minute swap storm during
which the computer was virtually useless.
I discovered that if I limited the RSS of the link process so that it left
a few megs of memory free then I could read mail or look around the web
while the link was running. This of course slowed down the link, but I
was supprised by how little it suffered. It might have been 10% slower
and the tradeoff I got was to be able to use the machine while it was
working rather than sitting there looking at it.
Thanks,
Jim
prev parent reply other threads:[~2003-06-13 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 20:55 limit resident memory size Muthian Sivathanu
2003-06-12 22:15 ` David Schwartz
2003-06-12 23:03 ` Muthian Sivathanu
2003-06-12 23:13 ` Timothy Miller
2003-06-12 23:37 ` David Schwartz
2003-06-13 17:02 ` Muthian Sivathanu
2003-06-13 2:07 ` Rik van Riel
2003-06-13 10:21 ` jlnance [this message]
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=20030613102139.GA769@ncsu.edu \
--to=jlnance@unity.ncsu.edu \
--cc=linux-kernel@vger.kernel.org \
/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