Easter sermon: Of kernels and slocate [was: Slocate hates me (was:Prelink hates me)]

[Arjan van de Ven]

> We have a similar problem with databases: reports that need to scan an
> entire database fill the database cache with unnecessary data, while
> only a fraction of the database is usually active.  In the database
> package I am familiar with, you can set a parameter that limits how much
> database cache the reports are allowed to use.  It seems like a similar
> parameter for file system cache could be created for programs like
> slocate.

what you mention actually exists, it's called O_DIRECT.
however that only works for data, not filesystem metadata. slocate only
does metadata so it doesn't gain from this....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20040412/944d5581/attachment.sig>