Re: [PATCH 0/8] Codespeed perf results
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Dec 13, 2017, 16:18 UTC
- Message-ID
- <CAP8UFD3Q4h-aYBDABSPOW948LQYVydWZ1hLPAD+kr9ZpXVZiaQ@mail.gmail.com>
- In-Reply-To
- <53BD7DB89F12403F974A7D2201CC7307@PhilipOakley>
On Wed, Dec 13, 2017 at 5:02 PM, Philip Oakley <philipoakley@iee.org> wrote:
Show 9 quoted lines
>> The end goal would be to have such a server always available to track >> how the different git commands perform over time on different kind of >> repos (small, medium, large, ...) with different optimizations on and >> off (split-index, libpcre2, BLK_SHA1, ...) > > Dumb question: is this expected to also be able to do a retrospective on the > performance of appropriate past releases? That would allow immediate > performance comparisons, rather than needing to wait for a few releases to > see the trends.
Yeah, sure. For example in the perf.conf file above there is "dirsOrRevs = v2.12.0 v2.13.0" which means that tests will be performed on v2.12.0 and v2.13.0.