Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade the openebs/tests-tpcc-client container to perform parallel database load in tpcc-runner.sh #19

Open
ksatchit opened this issue Sep 27, 2018 · 2 comments
Labels

Comments

@ksatchit
Copy link
Member

ksatchit commented Sep 27, 2018

Is this a BUG REPORT or FEATURE REQUEST?

FEATURE REQUEST

What happened:

  • The openebs/tests-tpcc-client container currently performs the following step to load the database with entries (as per the number of warehouses specified in the tpcc.conf benchmark config file) before running the actual benchmark test (tpcc_start) :-

./tpcc_load -h <DB_SERVER_IP> -P3306 -d<DB_NAME> -u <DB_USER> -p <DB_PASSWORD> -w

This is a sequential process that increases in duration with the number of warehouses specified, thereby delaying the start of the actual benchmark.

What you expected to happen:

  • The benchmark test should get started quicker.

How to fix it?

  • This process can be made quicker by running multiple parallel tpcc_load operations on a subset of warehouses. There is already a script (load.sh) provided by percona in the tpcc-mysql repo which does this - we need to use it in the tpcc-runner.sh with the logic to identify completion of all tpcc_load processes before proceeding to start the benchmark

How to test it?

@dreamerHarshit
Copy link

dreamerHarshit commented Oct 3, 2018

@ksatchit i want to work on this issue.

@ksatchit
Copy link
Member Author

ksatchit commented Oct 4, 2018

Sure @dreamerHarshit ! Looking forward to the PR !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants