News for hackers. Stuff that matters.
Re:Supercharging the Git Commit Graph by Aissen on Thursday June 28, 2018 @05:58AM (#17415489)
I had to bite… The sqlite repository has only 20795 commits since May 2000 at the time of this writing: https://www.sqlite.org/src/timeline?udc=1&ss=m&n=100000&y=ci

This is the amount of commits that goes into Linux every ~5months.

Has anyone done any meaningful performance comparison between fossil and git?

Re:Supercharging the Git Commit Graph by reificator on Thursday June 28, 2018 @10:21AM (#17417061)
How does the number of commits in the SQLite repository make it unsuitable as alternate store for git metadata?
Re:Supercharging the Git Commit Graph by Aissen on Friday June 29, 2018 @03:58AM (#17423099)
@jasode's reply in this thread made a good summary of the two parallel discussions/quid pro quo:

- on filesystem vs sqlite (put git files in sqlite): there's a good benchmark on https://www.sqlite.org/fasterthanfs.html claiming sqlite is up to 35% faster than fs. I'd like to see the same benchmark with git's file pattern; also, it's a known issue with git that it was written for linux first, hence optimized against Linux (relatively) good fs performance (vs Windows and Mac at the time). Same with most OSS build systems that (over)use process forking, which is also very optimized in Linux.

- on Fossil vs git (why bother putting git files in sqlite and not directly jump to fossil?): that was my comment, and it relates to subject of this article (the commit-graph). I'm wondering if Fossil has seen the optimization that git has, with regards to number of commits, considering that sqlite is the only high-profile project that uses it. Maybe performance is supposed to be taken care of by the sqlite database itself ?

Edit: see https://www.fossil-scm.org/xfer/doc/trunk/www/stats.wiki for a fossil-provided performance analysis, that does a comparison with CVS (!).

Re:Supercharging the Git Commit Graph by adrianN on Thursday June 28, 2018 @07:39AM (#17416002)
The number of commits is not a very meaningful metric.
Re:Supercharging the Git Commit Graph by masklinn on Thursday June 28, 2018 @07:47AM (#17416051)
It's very much a meaningful metric when the entire point of TFA is caching the commits graph. This is only an issue when you actually have lots of commits, and even more so a very branchy graph.
Re:Supercharging the Git Commit Graph by adrianN on Thursday June 28, 2018 @08:22AM (#17416252)
It's not a meaningful metric when discussing whether to use sqlite as storage for git instead of files in the .git directory.
Re:Supercharging the Git Commit Graph by jasode on Thursday June 28, 2018 @09:11AM (#17416539)
>It's not a meaningful metric when discussing whether to use sqlite as storage for git instead of files in the .git

There are 2 different conversations happening.

You seemed to be responding to ggp (rakoo) "sqlite db vs files".

However masklinn was responding to gp (Aissen) question of "Fossil vs Git" performance and a charitable reading would be comparing the Fossil algorithms (also affected by combination with underlying SQLite db engine algorithm) for commit searches, graph traversal, etc. In that case, the high number of commits and total repository size to stress test Fossil/Git would be very relevant.

An example post about Fossil scaling: https://www.fossil-scm.org/xfer/technote/be8f2f3447ef2ea3344...