====================================================================================================
SYSBENCH BENCHMARK REPORT 
====================================================================================================
MACHINE:  Drizzle-build-n04
RUN ID:   235
RUN DATE: 2011-06-18T23:18:42.298989
WORKLOAD: innodb_1000K_readwrite
SERVER:   drizzled
VERSION:  staging
REVISION: 2341
COMMENT:  2341: Mark Atwood 2011-06-18 [merge] merge 
lp:~stewart/drizzle/bug658673-DD-use-MAXIMUM_IDENTIFIER_LENGTH
====================================================================================================

TRENDING OVER LAST 5 runs 
Conc   TPS     % Diff from Avg   Diff       Min        Max        Avg        
STD       
====================================================================================================
16     1721.16       +0.11%       1.92    1659.21    1773.94    1719.24      
30.76
32     1744.45       -0.89%     -15.66    1678.45    1813.72    1760.11      
34.91
64     1742.96       -2.11%     -37.59    1698.05    1825.12    1780.55      
35.98
128    1691.33       -1.76%     -30.34    1670.00    1756.22    1721.67      
24.01
256    1526.55       -1.41%     -21.76    1515.53    1579.72    1548.31      
20.79
512    1329.50       -1.14%     -15.32    1327.57    1353.63    1344.82       
8.70
1024   987.37       -3.34%     -34.08     970.80    1041.83    1021.45      
19.13
====================================================================================================

TRENDING OVER Last 20 runs 

Conc   TPS     % Diff from Avg   Diff       Min        Max        Avg        
STD       
====================================================================================================
16     1721.16       +0.42%       7.20    1630.61    1799.48    1713.96      
38.72
32     1744.45       +1.03%      17.77    1610.99    1813.72    1726.69      
51.98
64     1742.96       -0.63%     -10.98    1664.53    1847.42    1753.93      
43.58
128    1691.33       -0.75%     -12.82    1644.19    1756.22    1704.15      
27.20
256    1526.55       -0.28%      -4.21    1478.51    1579.72    1530.76      
26.08
512    1329.50       -0.77%     -10.28    1319.46    1363.34    1339.79      
10.22
1024   987.37       -2.99%     -30.41     954.94    1042.91    1017.78      
20.87
====================================================================================================

TRENDING OVER ALL runs 

Conc   TPS     % Diff from Avg   Diff       Min        Max        Avg        
STD       
====================================================================================================
16     1721.16       -2.10%     -36.90    1177.28    1913.94    1758.06      
75.01
32     1744.45       +0.97%      16.71    1448.82    1853.08    1727.75      
61.69
64     1742.96       +0.39%       6.69    1480.63    1872.32    1736.27      
53.31
128    1691.33       -0.08%      -1.38    1401.59    1771.41    1692.71      
46.26
256    1526.55       +0.41%       6.28    1268.10    1580.87    1520.27      
38.71
512    1329.50       -0.34%      -4.57    1077.71    1380.41    1334.07      
33.41
1024   987.37       -2.20%     -22.23     880.04    1065.34    1009.60      
30.41
====================================================================================================
FULL REVISION COMMENTARY:

  2338.2.23: Stewart Smith 2011-06-18 use MAXIMUM_IDENTIFIER_LENGTH for 
INFORMATION_SCHEMA.COLUMN_DOMAIN_USAGE columns
  2338.2.22: Stewart Smith 2011-06-18 use MAXIMUM_IDENTIFIER_LENGTH for 
INFORMATION_SCHEMA.COLUMN_PRIVILEGES columns
  2338.2.21: Stewart Smith 2011-06-18 use MAXIMUM_IDENTIFIER_LENGTH for 
INFORMATION_SCHEMA.CONSTRAINT_COLUMN_USAGE columns
  2338.2.20: Stewart Smith 2011-06-18 use MAXIMUM_IDENTIFIER_LENGTH for 
INFORMATION_SCHEMA.CONSTRAINT_TABLE_USAGE columns
  2338.2.19: Stewart Smith 2011-06-18 use MAXIMUM_IDENTIFIER_LENGTH for 
INFORMATION_SCHEMA.ROUTINE_COLUMNS columns
  2338.2.18: Stewart Smith 2011-06-18 use MAXIMUM_IDENTIFIER_LENGTH for 
INFORMATION_SCHEMA.ROUTINES columns
  2338.2.17: Stewart Smith 2011-06-18 use MAXIMUM_IDENTIFIER_LENGTH for 
INFORMATION_SCHEMA.TABLE_CONSTRAINTS columns
  2338.2.16: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
INFORMATION_SCHEMA.TABLE_PRIVILEGES columns
  2338.2.15: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
INFORMATION_SCHEMA.VIEW_COLUMN_USAGE columns
  2338.2.14: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
INFORMATION_SCHEMA.VIEW_TABLE_USAGE columns
  2338.2.13: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
INFORMATION_SCHEMA.VIEWS columns
  2338.2.12: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
DATA_DICTIONARY.INNODB_INTERNAL_TABLES columns
  2338.2.11: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
DATA_DICTIONARY.COLUMNS columns
  2338.2.10: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
DATA_DICTIONARY.FOREIGN_KEYS columns
  2338.2.9: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
INDEX_PARTS columns
  2338.2.8: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for INDEXES 
columns
  2338.2.7: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
TABLE_CONSTRAINTS columns
  2338.2.6: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
SHOW_TABLES columns
  2338.2.5: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
SHOW_TEMPORARY_TABLES columns
  2338.2.4: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
DATA_DICTIONARY.TABLE_CACHE columns
  2338.2.3: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
DATA_DICTIONARY.TABLE_DEFINITION_CACHE columns
  2338.2.2: Stewart Smith 2011-06-17 use MAXIMUM_IDENTIFIER_LENGTH for 
DATA_DICTIONARY.TABLES columns
  2338.2.1: Stewart Smith 2011-06-17 use TABLE_COMMENT_MAXLEN define in 
schema_dictionary instead of hard coded 2048

_______________________________________________
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