Re:Why Perforce is more scalable than Git
by andr on Sunday March 15, 2009 @06:11AM
(#516746)
The article never actually says why Perforce is more scalable, except that you have "an IT department taking care of it."
[ Parent
| on HN ]
Re:Why Perforce is more scalable than Git
by silentbicycle on Sunday March 15, 2009 @10:07AM
(#516832)
Perforce only scans through everything when you update or scan for changed files, but mostly tracks changes file by file. Git (and mercurial) work with the state of the tree as a whole for most operations, because this makes handling searching, branching, merging, etc. much nicer, but it means that when you have gigantic binary files just sitting around, it takes time scanning them as well.
Why not cache the MD5/SHA1 hashes and only update them when the timestamp of the file changes?
Re:Why Perforce is more scalable than Git
by silentbicycle on Sunday March 15, 2009 @12:48PM
(#516948)
Mercurial does, by default. I'm almost certain git already does, too.