News for hackers. Stuff that matters.
Re:Some bad Git situations and how I got myself out of them by witty_username on Friday September 09, 2016 @12:52PM (#12463966)
Did you run hg grep once before to keep it in the disk cache?
Re:Some bad Git situations and how I got myself out of them by jlebar on Friday September 09, 2016 @01:21PM (#12464245)
It seems I cannot post a performance comparison without people asking about disk caches. :)

First of all, if I just cloned the repos, they should be in disk cache. My machine has 64GB of RAM.

Second of all, if they're not in disk cache, what on earth is hg doing that it takes 16 seconds to read them all in? Eigen is not that big, and I have a fast SSD.

Third of all, you can run the tests yourself -- I gave you the exact commands to try. "I tried it and my results are X" is a much better contribution to the discussion.

Fourth of all, yes, I ran the benchmarks multiple times in a row to check whether disk cache was at play. It was not. :)

Re:Some bad Git situations and how I got myself out of them by witty_username on Friday September 09, 2016 @01:46PM (#12464472)
> It seems I cannot post a performance comparison without people asking about disk caches. :)

Sorry, the speedup was very great so it almost seemed like something else was causing it. Thanks for the benchmarks.

> Third of all, you can run the tests yourself -- I gave you the exact commands to try. "I tried it and my results are X" is a much better contribution to the discussion.

That's true; I'm lazy.

Actually, I was thinking more of the disk cache of loading hg, not the repo (Python programs tend to have a great speedup through the disk cache).

Re:Some bad Git situations and how I got myself out of them by mjevans on Friday September 09, 2016 @01:11PM (#12464154)
I think the implication is that the freshly checked out state of the files was used.

I do agree that reproducible differences in performance should be measured, not single tests.