Re: Mercurial 0.3 vs git benchmarks

From: Florian Weimer <fw@deneb.enyo.de>
Date: Apr 27, 2005, 20:55 UTC
Message-ID: <874qds5489.fsf@deneb.enyo.de>
In-Reply-To: <20050427190144.GA28848@cip.informatik.uni-erlangen.de>

* Thomas Glanzmann:

Show 8 quoted lines

>> Directory hashing slows down operations that do linear sweeps through 
>> the filesystem reading every single file, simply because without 
>> dir_index, there is likely to be a correlation between inode order and 
>> directory order, whereas with dir_index, readdir() returns entries in 
>> hash order.
>
> thank you for the awareness training. Than mutt should be slower, too.
> Maybe I should repeat that tests.

Benchmarks are actually a bit tricky because as far as I can tell, once you hash the directories, they are tainted even if you mount your file system with ext2.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.