On Tue, May 13, 2014 at 9:24 PM, Stefan Beller wrote:
>> That is clocked at 800 MHz. A repository at this size deserves a
>> better CPU. At 2.5 GHz we spend 183.228ms on loading the index. A
>> reasonable number to me. If we scale other parts of git-status as well
>> as this, we should be able to make "git status" within 1 or 2 seconds.
>>
>
> Which harddrive do you use? Traditional or SSDs?
Traditional
> Does have harddrive loading time significant impact here? (just a
> guess/question)
In the hot cache case, I assume the index stays in OS cache anyway so
hard drive should not impact much (the other parts of git-status like
index refresh or untracked file listing is a different story and some
may fall out of cache). My laptop has 4G ram, with my repeated tests,
I guess the index (even 200mb) stayed in the cache (but did not really
verify it).
--
Duy
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
