-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian Aker wrote: > Hi! > > Rerun the regression on the sub versions.
Will do. Benchmarks have been running solidly now for >30 hours, and they're getting close to being done for readonly workload. I'll push the sub revisions into the bench queue shortly. > Either it is the STL or a > change in replication (I would bet on replication). Replication? Never! Nothing I wrote could ever cause a regression! ;P Technically, the replication stuff should be a NOOP when no replicators or appliers are registered...but you never know! :) Cheers! Jay > Cheers, > -Brian > > On May 1, 2009, at 9:11 PM, Jay Pipes wrote: > > Hi! > > Somewhere in r990, we have had a significant regression, most evident in > concurrency levels greater than 128 concurrent connections: > > +-----------+-------------+-------------+ > | version | concurrency | tps | > +-----------+-------------+-------------+ > | trunk-989 | 2 | 1050.630000 | > | trunk-989 | 4 | 1417.433333 | > | trunk-989 | 8 | 1942.686667 | > | trunk-989 | 16 | 2612.166667 | > | trunk-989 | 32 | 3389.150000 | > | trunk-989 | 64 | 3944.433333 | > | trunk-989 | 128 | 3924.076667 | > | trunk-989 | 256 | 2964.776667 | > | trunk-989 | 512 | 1981.050000 | > | trunk-989 | 1024 | 1273.133333 | > | trunk-989 | 2048 | 563.350000 | > | trunk-990 | 2 | 1038.133333 | > | trunk-990 | 4 | 1381.933333 | > | trunk-990 | 8 | 1897.276667 | > | trunk-990 | 16 | 2547.196667 | > | trunk-990 | 32 | 3331.570000 | > | trunk-990 | 64 | 3896.483333 | > | trunk-990 | 128 | 3850.016667 | > | trunk-990 | 256 | 2331.543333 | > | trunk-990 | 512 | 1862.316667 | > | trunk-990 | 1024 | 1103.903333 | > | trunk-990 | 2048 | 436.976667 | > +-----------+-------------+-------------+ > > The above TPS column is the average of 3 iterations of a readonly > sysbench workload for the revision/concurrency pair. > > Unfortunately, r990 was a very big revision with a lot of changes: > > http://bazaar.launchpad.net/~drizzle-developers/drizzle/development/revision/990 > > > This makes it very difficult to tell what precisely has caused the > regression. I'd like to suggest that going forward, we really try to > keep the size of merges and commits small so that it is easier to tell > where regressions occur. > > Anyone interested in looking through the commit diff above is welcome to > suggest ideas where regression may have occurred...but it might be, like > Brian says, death by a thousand cuts... > > Cheers! > > Jay > -- > _______________________________________________________ > Brian "Krow" Aker, brian at tangent.org > Seattle, Washington > http://krow.net/ <-- Me > http://tangent.org/ <-- Software > _______________________________________________________ > You can't grep a dead tree. > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn8V+IACgkQ2upbWsB4UtGx9wCfdk1IN8XYl2Mu13jyldVqDc7t lfMAnA7iy7N6T2zZoNokITwP0UxYh5pe =CEKi -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
