====================================================================================================
SYSBENCH BENCHMARK REPORT 
====================================================================================================
MACHINE:  r815-test2
RUN ID:   342
RUN DATE: 2010-12-15T18:15:13.279059
WORKLOAD: innodb_1000K_readwrite
SERVER:   drizzled
VERSION:  staging
REVISION: 1996
COMMENT:  1996: Lee Bieber 2010-12-15 [merge] Merge Andrew - fix bug 628912: 
Crash / segfault in drizzled::Item_func::arguments (this=0x35) at 
./drizzled/function/func.h
====================================================================================================

TRENDING OVER LAST 5 runs 
Conc   TPS     % Diff from Avg   Diff       Min        Max        Avg        
STD       
====================================================================================================
16     1694.45       +0.89%      14.94    1655.97    1706.33    1679.51      
17.14
32     1926.37       -0.86%     -16.72    1918.05    1977.46    1943.09      
20.14
64     1425.49       +0.10%       1.41    1406.70    1460.90    1424.08      
13.72
128    1132.03       +3.51%      38.40    1046.79    1143.74    1093.63      
37.23
256    870.54       -1.29%     -11.42     862.98     895.20     881.96       
8.28
512    620.23       +0.92%       5.64     604.77     624.19     614.59       
6.17
1024   397.97       +0.35%       1.40     391.18     399.01     396.57       
2.17
====================================================================================================

TRENDING OVER Last 20 runs 

Conc   TPS     % Diff from Avg   Diff       Min        Max        Avg        
STD       
====================================================================================================
16     1694.45       +0.59%       9.86    1630.16    1737.63    1684.59      
22.15
32     1926.37       -1.28%     -25.01    1890.78    2078.46    1951.38      
35.42
64     1425.49       -0.08%      -1.15    1270.83    1490.73    1426.64      
40.67
128    1132.03       +3.88%      42.31    1042.21    1148.68    1089.72      
30.20
256    870.54       -1.39%     -12.26     860.89     912.68     882.80      
10.47
512    620.23       +0.89%       5.45     604.39     630.27     614.78       
6.16
1024   397.97       +0.16%       0.63     383.67     402.55     397.34       
3.77
====================================================================================================

TRENDING OVER ALL runs 

Conc   TPS     % Diff from Avg   Diff       Min        Max        Avg        
STD       
====================================================================================================
16     1694.45       +0.48%       8.07     389.06    1869.76    1686.38     
178.50
32     1926.37       -5.42%    -110.33     511.98    2395.61    2036.70     
219.53
64     1425.49       -2.98%     -43.80     899.67    1721.72    1469.29      
92.07
128    1132.03       +1.52%      17.00     638.89    1345.78    1115.03      
81.47
256    870.54       -1.64%     -14.54     453.75    1034.59     885.08      
75.06
512    620.23       -0.42%      -2.59     312.83     781.01     622.82      
64.47
1024   397.97       -2.22%      -9.03     361.44     487.49     407.00      
26.42
====================================================================================================
FULL REVISION COMMENTARY:

  1995.1.2: Lee Bieber 2010-12-15 [merge] Merge Andrew - fix bug 628912: Crash 
/ segfault in drizzled::Item_func::arguments (this=0x35) at 
./drizzled/function/func.h
    1993.4.3: Andrew Hutchings 2010-12-14 OK, so it turns out, push_back on a 
vector you are currently iterating over is bad because the vector makes a copy 
of itself in another memory position.
    1993.4.2: Andrew Hutchings 2010-12-13 Add pcrews' test case
    1993.4.1: Andrew Hutchings 2010-12-13 vector push_back on COND_CMP struct 
was causing an extra empty element to be added to the vector when vector size 
reached 3 (compiler bug?).  Changed to std::pair pointers instead.
  1995.1.1: Lee Bieber 2010-12-15 [merge] Merge Andrew - 663919: next query 
after KILL QUERY will error
    1994.3.1: Andrew Hutchings 2010-12-14 Don't kill a query with KILL QUERY if 
there is no query running

_______________________________________________
Mailing list: https://launchpad.net/~drizzle-benchmark
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-benchmark
More help   : https://help.launchpad.net/ListHelp

Reply via email to