[lkml]   [2007]   [Jul]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: RFT: updatedb "morning after" problem [was: Re: -mm merge plans for 2.6.23]
On 07/28/2007 09:35 AM, Rene Herman wrote:

> By the way -- I'm unable to make my slocate grow substantial here but
> I'll try what GNU locate does. If it's really as bad as I hear then
> regardless of anything else it should really be either fixed or dumped...

Yes. GNU locate is broken and nobody should be using it. The updatedb from
(my distribution standard) "slocate" uses around 2M allocated total during
an entire run while GNU locate allocates some 30M to the sort process alone.

GNU locate is also close to 4 times as slow (although that ofcourse only
matters on cached runs anyways).

So, GNU locate is just a pig pushing things out, with or without any added
VFS cache pressure from the things it does by design. As such, we can trust
people complaining about it but should first tell them to switch to halfway
sane locate implementation. If you run memory hogs on small memory boxes,
you're going to suffer.

Leaves the fact that swap-prefetch sometimes helps alleviate these and other
kinds of memory-hog situations and as such, might not (again) be a bad idea
in itself.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-07-28 10:55    [W:0.264 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site