lp:~mdcallag/sysbench/0.4-dev

Created by Mark Callaghan and last modified
Get this branch:
bzr branch lp:~mdcallag/sysbench/0.4-dev
Only Mark Callaghan can upload to this branch. If you are Mark Callaghan please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Mark Callaghan
Project:
sysbench
Status:
Development

Recent revisions

81. By Mark Callaghan

make counter work despite optimizer

80. By Mark Callaghan

use more precision for times
change update-non-key field to match what is used by jmongosysbench

79. By Mark Callaghan

add --oltp-inlist-sum that adds the query:
  select sum(k) from TABLE where id in (....)
and there are 80 non-consecutive id values in the inlist.

78. By Mark Callaghan

add incupdate2 test
make some stats per-interval

77. By Mark Callaghan

Fix a bug in the previous change to fix the fileio race

76. By Mark Callaghan

Fix race conditions in sysbench fileio. There were a few global variables updated without
mutex protection. Remove fsync_mutex as the global sysbench mutex is sufficient. I don't
think fine-grained locking is needed in this code. I was getting errors and early
test failures when running this with multiple threads and fsync enabled.

75. By Mark Callaghan

Use somewhat random data for the 'k' and 'c' and 'pad' columns to make it harder to compress.

74. By Mark Callaghan

Change --batch stats to be per interval, not cumulative

73. By Mark Callaghan

Add
--oltp-simple-update to get read-write workload with updates on non-indexed column for simple test mode.
--oltp-point-select-mysql-handler-read-open-close to use HANDLER_OPEN_READ_CLOSE for tests that use HANDLER

72. By Mark Callaghan

Add --oltp-test-mode=incupdate and --oltp-test-mode=incinsert for new tests.
With 'incupdate' each thread does nothing but updates to increment the integer
stored in column 'c'. With 'incinsert' the same is done using
INSERT ... ON DUPLICATE KEY UPDATE c = c + 1. The table of 'c' in the sbtest
table is not changed from char. I have a use case for which the performance
of these statements matter.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.