[PATCH] performance history specification

[Jan Balster]

John Arbash Meinel wrote:
> Jan Balster wrote:
>>> Robert Collins wrote:
>>>> On Thu, 2006-07-13 at 23:21 -0500, John Arbash Meinel wrote:
>>> ...
>>>> I'd like it in asap so that we can put a cron job on bazaar-vcs.org
>>>> running HEAD with this, so we have object performance stats for all the
>>>> benchmarks.
>>>>
>>> Hi Rob,
>>>
>>> I created a preliminary web page (and a little cron job on codespeak.net)
>>> for showing performance numbers from the bzr.dev main branch.
>>> The page is available at http://codespeak.net/bzr/perf_history/summary_bzr.dev.html
>>>
>>> It's designed to give an overview of the development on the performance front.
>>> Comments/thoughts? (let's talk about fonts and colors later  ;)  )
>>>
>>> Some Information:
>>> The performance tests where added to the main branch in revision 1729
>>> (2006-05-18), but it contains an error. The error was fixed in 1744 but for
>>> some reasons I started with revision 1749 (2006-06-07). However, a new data set
>>> should be added every day.
>>>
>>> cheers,
>>>    Jan
>>>
> 
> Looks pretty nice. The small graph is pretty cute.

:)

> I wonder about having columns that you can expand. When you have a
> couple hundred columns it is a little bit difficult to find what you
> want. But sometimes you might want to expand a certain region, to find
> what revno introduced a performance hit.

Sure, that would be nice. And I'm planning to add that, but I have to think a
bit about the user interface for that use case.
Neither I want to have to generate 100+ pages and link between them nor I want
to add a lot of javascript. But that are details ;)

> Like I think the performance jump for:
> InvBenchmark.test_make_10824_inv_entries
> between 1839 and 1859 was probably caused by my
> 
> 1851 (jam) support mac-normalization for unicode files.

Yes, it's revision 1851 which introduced the performance hit.

> You also have every 10, but you are missing 1849.

Yes, some tests fail because of the missing bzrdir. prefix in
benchmarks/__init__.py and the tests weren't added to the overview. That will be
fixed soon.

> John
> =:->

cheers,
  Jan