On 21 August 2016 at 19:02, Maciej Fijalkowski email@example.com wrote:
Let's not have it called "bzr" though because it gives the wrong impression. The same way unladen swallow added a benchmark and called it "django" while not representing django very well. That said, likely not very many people use bzr, but still, would be good if it's called bzr-pyc or simpler - have a benchmark that imports a whole bunch of pyc from a big project (e.g. pypy :-)
Yeah, I assume the use of bzr for this purpose is mainly an accident of history - adopting a non-trivial cross-platform Python command line application, rather than putting together a synthetic benchmark like Tools/importbench that may not be particular representative of real workloads (which can use techniques like lazy module imports to defer startup costs until those features are actually needed).
Perhaps call the benchmark "bzr-startup" to emphasize the aim is to measure how long it takes bzr to start in general, moreso than how long it takes to print the help message?