benchmark: add a score of new rename related benchmark
We test a wide array of cases to better track how they will evolves depending of the copy-tracing method. Some might be a bit redundant, but there is enough small variation than it is useful to track many variants. Ideally, we could run various pair in the same area, but that would greatly increase the run time. (the current change already have a quite visible impact). Appropriate benchmark variable have been set for repository. We restricted them to zstd + sparse-revlog variante to reduce run time.
Please register or sign in to comment