On 26 May 2008, Juliusz Chroboczek stated: > All modern file-systems use either B-trees or B*-trees for > directories.
As an aside, ext[234]fs do not, nor will they ever as far as I know. FFS does not. A lot of Polipo-using systems probably run atop those :/ (ext3fs and ext4fs have a hack whereby filenames are reordered such that they can be looked up by means of a hash lookup, which is just about as good for most purposes.) >> -- I can set BerkeleyDB not to fsync until the buffers are full, >> this means that my laptop -- when on battery -- will not wake the HDD >> even when I've written a cache entry; > > Polipo will never fsync. That's the performance problem in Firefox, for what it's worth: the db fsync()s fairly frequency, and ext3 has to sync the journal whenever an fsync() happens. This effectively turns fsync() and fdatasync() into sync() on that filesystem :/ >> -- it works much better than the file system, for large data sets >> with a lot of keys; > > Please don't use broken file-systems. Xfs and Reiserfs work fine with > ñPolipo, and even ext3 appears to be getting better. That's the effect of the hashing hack described above, I expect. -- `If you are having a "ua luea luea le ua le" kind of day, I can only assume that you are doing no work due [to] incapacitating nausea caused by numerous lazy demons.' --- Frossie ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Polipo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/polipo-users
