From: Rilson N. <ri...@it...> - 2006-03-15 17:45:20
|
Hi there, =20 I am using OSDL-DBT 0.37 with MySQL 5.0.12. The db size is 100 warehouses and the duration of my tests is 2 hours. I have run a lot of tests with this configuration and, invariably, at the end of the tests the %txn mix never sums up to 100%. In general, the number is round 97%.=20 I would like to know what I could do get this sum nearer 100%. Ideally, I would like to increase the number of new order txns in order to get a higher NOTPM. In time, DBT2 has %mix constraints like TPC-C does? (eg, delivery must be at least 4%). =20 Thanks and regards, =20 -Rilson |
From: Mark W. <ma...@os...> - 2006-03-15 17:54:25
|
On Wed, 15 Mar 2006 14:44:59 -0300 "Rilson Nascimento" <ri...@it...> wrote: > Hi there, > > > > I am using OSDL-DBT 0.37 with MySQL 5.0.12. The db size is 100 > warehouses and the duration of my tests is 2 hours. > > I have run a lot of tests with this configuration and, invariably, at > the end of the tests the %txn mix never sums up to 100%. In general, the > number is round 97%. Interesting, sounds like a math error. I wonder if it's a rounding error in the mix_analyzer.pl script. > I would like to know what I could do get this sum nearer 100%. Ideally, > I would like to increase the number of new order txns in order to get a > higher NOTPM. In time, DBT2 has %mix constraints like TPC-C does? (eg, > delivery must be at least 4%). Yes, there is a default mix constraint that conforms to the TPC-C specification. You can increase the new order transaction mix by decreasing the other transaction mixes using the -q, -r, -e, and -t flags with the driver binary. Mark |
From: Koji F. <k....@jp...> - 2007-02-02 06:56:19
|
Hi , Mark Wong wrote: > On Wed, 15 Mar 2006 14:44:59 -0300 > "Rilson Nascimento" <ri...@it...> wrote: > >> Hi there, >> >> >> >> I am using OSDL-DBT 0.37 with MySQL 5.0.12. The db size is 100 >> warehouses and the duration of my tests is 2 hours. >> >> I have run a lot of tests with this configuration and, invariably, at >> the end of the tests the %txn mix never sums up to 100%. In general, the >> number is round 97%. > > Interesting, sounds like a math error. I wonder if it's a rounding > error in the mix_analyzer.pl script. Version 0.39 script mix_analyzer.pl While reading mix.log and Waitng for START record. Each transaction count is reset to Zero. But total_response_time and total_transaction_count are not reseted. Therefore total Transaction %mix was not 100%. When i set Duration to 4200Sec Total %mix was 70% Is this relate to V0.37 total %mix 97%? >> I would like to know what I could do get this sum nearer 100%. Ideally, >> I would like to increase the number of new order txns in order to get a >> higher NOTPM. In time, DBT2 has %mix constraints like TPC-C does? (eg, >> delivery must be at least 4%). > > Yes, there is a default mix constraint that conforms to the TPC-C > specification. You can increase the new order transaction mix by > decreasing the other transaction mixes using the -q, -r, -e, and -t > flags with the driver binary. > > Mark Koji Fukui |
From: <ma...@gm...> - 2007-02-02 23:29:54
|
On 2/1/07, Koji Fukui <k....@jp...> wrote: > Hi , > > Mark Wong wrote: > > On Wed, 15 Mar 2006 14:44:59 -0300 > > "Rilson Nascimento" <ri...@it...> wrote: > > > >> Hi there, > >> > >> > >> > >> I am using OSDL-DBT 0.37 with MySQL 5.0.12. The db size is 100 > >> warehouses and the duration of my tests is 2 hours. > >> > >> I have run a lot of tests with this configuration and, invariably, at > >> the end of the tests the %txn mix never sums up to 100%. In general, the > >> number is round 97%. > > > > Interesting, sounds like a math error. I wonder if it's a rounding > > error in the mix_analyzer.pl script. > > Version 0.39 script mix_analyzer.pl > While reading mix.log and Waitng for START record. > Each transaction count is reset to Zero. > But total_response_time and total_transaction_count are not reseted. > Therefore total Transaction %mix was not 100%. > When i set Duration to 4200Sec Total %mix was 70% > > Is this relate to V0.37 total %mix 97%? Hi there! Whoops, sounds like an error with those version. I didn't double check that but the logic now resides in this file: http://crucible.svn.sourceforge.net/viewvc/crucible/Test-Parser/lib/Test/Parser/Dbt2.pm?view=markup I think the relevant function start about line 226. I've changed the logic so that no stats are collected at line 290 until the START tag is found at line 330. Does that look ok to you? Regards, Mark |