[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [svnbench] Failed to build Revision: 1449572.

From: Neels Hofmeyr <neels_at_elego.de>
Date: Wed, 27 Feb 2013 18:35:25 +0100

On Wed, 27 Feb 2013 09:17:36 -0800
Ben Reser <ben_at_reser.org> wrote:

> On Wed, Feb 27, 2013 at 8:53 AM, Neels Hofmeyr <neels_at_elego.de> wrote:
> > (Simply uncommenting now would change the test case and could make
> > the new runs too different from the old runs, decreasing quality of
> > comparison. So it needs some checking and decisions too.)
>
> Maybe duplicate the copy test with a different name e.g. copy+wc and
> then you'll start getting comparisons with that without impacting the
> existing comparisons.

The benchmark initially was just a quick test for me, trying to write
down concrete 1.7.0 numbers in a magazine article. So I used a pseudo
random sequence that decides which modification to make. Just so I
didn't have to conjure up hundreds of modifications manually. Later on,
I simply clamped the initial random seed to get identical runs.

So if something else happens somewhere along the way, all the remaining
actions are impacted, simply because the random sequence plays out
differently.

I could of course simply *append* actions, now that I think of
it :) -- that should be quick and easy, in fact.

But I would anyway like to further reduce the number of propset/propget
benchmarks, because they just unnecessarily blow up the database
storage. That's why I'm considering a "complete" review anyway...

~Neels

Received on 2013-02-27 18:36:12 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.