#3 F1Season misaligns data

[Sharif Alexandre]

When correlating the F1Season data with the graphs
generated, it appears that the data is incorrectly
reported in the F1Season file. In the example below,
it appears that the write data is reported 4 times for
objects:3000, then read data is reported 4 times for
objects:10000, etc.

Using the example below, and looking at the graphs, the
data should be reported as:

commitinterval:1000 objects:3000
[1] 787ms
[2] 122ms
[3] 62ms
[4] 47ms

--------------------------------------------
Melbourne
writes, reads and deletes unstructured flat objects of
one kind in bulk mode
-------------------------------------------------------------------------------------------

[1] write
[2] read
[3] read_hot
[4] delete

- JDBC
--- MySQL 5.0.13 (linux-db-1)

commitinterval:1000 objects:3000
[1] 787ms
[1] 122ms
[1] 62ms
[1] 47ms

commitinterval:1000 objects:10000
[2] 1441ms
[2] 151ms
[2] 67ms
[2] 109ms

[Andrew Zhang]

Logged In: YES
user_id=1672246
Originator: NO

Hi Sharif,

Is it still reproducible? Thanks!

Best regards,
Andrew Zhang