[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] [PATCH] arch speedups on big trees

From: Tom Lord
Subject: Re: [Gnu-arch-users] [PATCH] arch speedups on big trees
Date: Wed, 28 Jan 2004 12:23:39 -0800 (PST)

    > From: Chris Mason <address@hidden>

    > I'll make you a deal, add 15,000 files any project tree that you
    > work on constantly through the day.  Never change these files
    > aside from when you add them, and add them inside any directory
    > structure you like.

    > Use it for two weeks running basic commands like commit/changes and
    > pulling in changes from other branches.  At least once pull in 50 or
    > more changesets from another tree.  At the end of all of that, I'm
    > pretty confident you'll think arch isn't usable on big trees.  

    > I'm sure there are better ways to make it faster than my current code,
    > but I haven't seen a lot of other ideas discussed.

Were _I_ to do that, I would use tagline tags.

Were I working with such a tree actively, I'd expect to be able to
expected-case inventory it in a very small number of seconds --
perhaps even a fraction of a second depending on my hw.

I would _guess_ that you are mostly using explicit tags and that that
is a large part of the reason for your dissatisfaction.  That will,
currently, tend to stress either kernel caches or i/o bandwidth

So, one of the better ways to make things faster for your situation
would (most likely) be to extend the inode signature/id-tag
optimizations so that they work for explicit tags.  This has the
advantage of also being a much easier change to make.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]