4 ms·
The number of commits is not a very meaningful metric.
by adrianN 8y ago
The number of commits is not a very meaningful metric.
- masklinn 8y agoIt'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.
- adrianN 8y agoIt's not a meaningful metric when discussing whether to use sqlite as storage for git instead of files in the .git directory.
- jasode 8y ago>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/be8f2f3447ef2ea3344f8058b6733aa08c08336f https://www.fossil-scm.org/xfer/technote/be8f2f3447ef2ea3344...