From: "Daniele P." <daniele@interline.it>
To: xfs@oss.sgi.com
Subject: Re: xfsrepair memory consumption
Date: Fri, 23 Mar 2007 09:36:47 +0100 [thread overview]
Message-ID: <200703230936.47788.daniele@interline.it> (raw)
In-Reply-To: <20070321213611.GB1208@tuatara.stupidest.org>
On Wednesday 21 March 2007 22:36, Chris Wedgwood wrote:
> On Wed, Mar 21, 2007 at 12:08:27PM +0100, Daniele P. wrote:
> > Phase 6 still uses little more memory (killed!).
> > I will add more memory and will test later.
>
> Stupid question (Sorry, I didn't read the thread that carefully), is
> there any reason you can't just add swap-space and let it thrash a
> little?
Oh, it's less expensive (less typing) to add ram because it's a
virtual machine.
Finally using the 2.8.20-1 version requires 1 GB of memory vs 750 MB for
2.6.20-1.
Next time I will add more swap by default.
Regards,
Daniele P.
next prev parent reply other threads:[~2007-03-23 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703210843.TAA08491@larry.melbourne.sgi.com>
2007-03-21 11:08 ` xfsrepair memory consumption Daniele P.
2007-03-21 21:36 ` Chris Wedgwood
2007-03-23 8:36 ` Daniele P. [this message]
2007-03-20 14:32 Daniele P.
2007-03-20 22:13 ` David Chinner
2007-03-20 23:48 ` Barry Naujok
2007-03-21 8:35 ` Daniele P.
2007-03-21 8:34 ` Daniele P.
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=200703230936.47788.daniele@interline.it \
--to=daniele@interline.it \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.