From: "Andika Triwidada" <andika@gmail.com>
To: Rene Herman <rene.herman@gmail.com>
Cc: Robert Deaton <false.hopes@gmail.com>,
linux-kernel@vger.kernel.org, ck list <ck@vds.kolivas.org>,
linux-mm@kvack.org
Subject: Re: updatedb
Date: Thu, 26 Jul 2007 13:23:03 +0700 [thread overview]
Message-ID: <7e0bae390707252323k2552c701x5673c55ff2cf119e@mail.gmail.com> (raw)
In-Reply-To: <46A81C39.4050009@gmail.com>
On 7/26/07, Rene Herman <rene.herman@gmail.com> wrote:
> On 07/25/2007 07:15 PM, Robert Deaton wrote:
>
> > On 7/25/07, Rene Herman <rene.herman@gmail.com> wrote:
>
> >> And there we go again -- off into blabber-land. Why does swap-prefetch
> >> help updatedb? Or doesn't it? And if it doesn't, why should anyone
> >> trust anything else someone who said it does says?
>
> > I don't think anyone has ever argued that swap-prefetch directly helps
> > the performance of updatedb in any way
>
> People have argued (claimed, rather) that swap-prefetch helps their system
> after updatedb has run -- you are doing so now.
>
> > however, I do recall people mentioning that updatedb, being a ram
> > intensive task, will often cause things to be swapped out while it runs
> > on say a nightly cronjob.
>
> Problem spot no. 1.
>
> RAM intensive? If I run updatedb here, it never grows itself beyond 2M. Yes,
> two. I'm certainly willing to accept that me and my systems are possibly not
> the reference but assuming I'm _very_ special hasn't done much for me either
> in the past.
Might be insignificant, but updatedb calls find (~2M) and sort (~26M).
Definitely not RAM intensive though (RAM is 1GB).
>
> The thing updatedb does do, or at least has the potential to do, is fill
> memory with cached inodes/dentries but Linux does not swap to make room for
> caches. So why will updatedb "often cause things to be swapped out"?
>
[ snip ]
--
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:[~2007-07-26 6:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 15:30 howto get a patch merged (WAS: Re: -mm merge plans for 2.6.23) Kacper Wysocki
2007-07-25 16:01 ` Rene Herman
2007-07-25 17:15 ` Robert Deaton
2007-07-26 3:59 ` updatedb Rene Herman
2007-07-26 6:23 ` Andika Triwidada [this message]
2007-07-26 7:49 ` updatedb Rene Herman
2007-07-26 9:37 ` updatedb Andika Triwidada
2007-07-27 0:46 ` updatedb Jesper Juhl
2007-07-27 6:00 ` updatedb Rene Herman
2007-07-27 7:54 ` updatedb Mike Galbraith
2007-07-27 8:28 ` updatedb Rene Herman
2007-07-27 9:26 ` updatedb Mike Galbraith
2007-07-27 11:09 ` updatedb Rene Herman
2007-07-27 11:48 ` updatedb Mike Galbraith
2007-07-27 12:28 ` updatedb Rene Herman
2007-07-27 13:32 ` updatedb Tilman Schmidt
2007-07-26 6:39 ` updatedb Bongani Hlope
2007-07-26 6:56 ` updatedb Rene Herman
2007-07-26 7:08 ` updatedb Bongani Hlope
2007-07-26 8:01 ` updatedb Rene Herman
2007-07-26 21:25 ` updatedb Bongani Hlope
2007-07-26 9:58 ` updatedb Björn Steinbrink
2007-07-26 10:23 ` updatedb Björn Steinbrink
2007-07-26 11:00 ` updatedb Rene Herman
2007-07-26 13:54 ` Re: howto get a patch merged (WAS: Re: -mm merge plans for 2.6.23) Jos Poortvliet
2007-07-25 16:07 ` Ingo Molnar
2007-07-25 16:40 ` [ck] " Michael Chang
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=7e0bae390707252323k2552c701x5673c55ff2cf119e@mail.gmail.com \
--to=andika@gmail.com \
--cc=ck@vds.kolivas.org \
--cc=false.hopes@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rene.herman@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