sysbench-tpcc
sysbench-tpcc copied to clipboard
Sysbench scripts to generate a tpcc-like workload for MySQL and PostgreSQL
Implements the time flag for benchmark which was previously not parsed correctly.
./tpcc.lua --pgsql-host=10.10.10.10 --pgsql-port=5432 --pgsql-user=sysbench --pgsql-password=sysbench --pgsql-db=sysbench --threads=64 --tables=1 --scale=100 --trx_level=RC --db-ps-mode=auto --db-driver=pgsql prepare ./tpcc.lua --pgsql-host=10.10.10.10 --pgsql-port=5432 --pgsql-user=sysbench --pgsql-db=sysbench --pgsql-password=sysbench --threads=64 --tables=1 --scale=100 --trx_level=RC --db-ps-mode=auto --db-driver=pgsql --time=360 --report-interval=5 run sysbench 1.0.20...
The full error is > FATAL: `thread_run' function failed: ...cal/Cellar/sysbench/1.0.17_1/share/sysbench/tpcc_run.lua:648: bad argument #3 to 'format' (number expected, got nil) It seems to happen randomly, some long runs complete and some...
Postgresql column storage has a great impact on performance, optimize column storage to PLAIN or EXTERNAL.
The current implementation of the auto incremented primary key in the History table uses `id int NOT NULL AUTO_INCREMENT` for all database engines. However, the correct code for PostgreSQL should...
modify the lua to support pgsql's prepare and execute syntax.
In the delivery transaction, percona sysbench uses "SELECT FOR UPDATE" in ```SQL rs = con:query(([[SELECT no_o_id FROM new_orders%d WHERE no_d_id = %d AND no_w_id = %d ORDER BY no_o_id ASC...
According to the TPCC spec, for payment transaction, the warehouse choosing rule is as follows:  So for any worker, the home warehouse should be fixed across a full run....
When I run either 'prepare' or 'run' with the trx_level setting, I am getting the following message 'Unrecognized command line argument: --trx_level=RC'. I am running it on Postgres. For example:...
FATAL:'sysbench.cmdline.call_command' function failed: ./tpcc_common.lua:477:db_bulk_insert_next()
os:centos7.4 mysql:5.7.24 sysbench:1.0.15 sysbench-tpcc:2.2