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
Parallelize perf testing between servers #4868
Labels
Projects
Comments
oleg-piskunov
pushed a commit
that referenced
this issue
May 5, 2020
- Adding 2 servers (sh1, sh2) for performance testing. Additional gitlab-ci tags for perf testing: docker_sh1_perf and docker_sh2_perf. - Rebalance performance testing between servers. - Changing gitlab-ci tag for performance docker images from 'perf' to 'deploy'. Closes #4868
oleg-piskunov
pushed a commit
that referenced
this issue
May 8, 2020
- Adding 2 servers (sh1, sh2) for performance testing. Additional gitlab-ci tags for perf testing: docker_sh1_perf and docker_sh2_perf. - Rebalance performance testing between servers. - Changing gitlab-ci tag for performance docker images from 'perf' to 'deploy'. Closes #4868
oleg-piskunov
pushed a commit
that referenced
this issue
May 15, 2020
- Adding 2 servers (sh1, sh2) for performance testing. - Rebalance performance testing between servers: - sh1 (tag: docker_sh1_perf) used for benches: nosqlbench_hash, nosqlbench_tree - sh2 (tag: docker_sh1_perf) used for benches: ycsb_hash, ycsb_tree, cbench - sh3 (tag: docker_sh1_perf) used for benches: sysbench, tpcc - sh9 (tag: docker_perf_ssd) used for benches: linkbench_ssd - Changing gitlab-ci tag for performance docker images from 'perf' to 'deploy'. Closes #4868
oleg-piskunov
pushed a commit
that referenced
this issue
May 15, 2020
- Adding 2 servers (sh1, sh2) for performance testing. - Rebalance performance testing between servers: - sh1 (tag: docker_sh1_perf) used for benches: nosqlbench_hash, nosqlbench_tree - sh2 (tag: docker_sh2_perf) used for benches: ycsb_hash, ycsb_tree, cbench - sh3 (tag: docker_sh3_perf) used for benches: sysbench, tpcc - sh9 (tag: docker_perf_ssd) used for benches: linkbench_ssd - Changing gitlab-ci tag for performance docker images from 'perf' to 'deploy'. Closes #4868
kyukhin
pushed a commit
that referenced
this issue
May 28, 2020
- Adding 2 servers (sh1, sh2) for performance testing. - Rebalance performance testing between servers: - sh1 (tag: docker_sh1_perf) used for benches: nosqlbench_hash, nosqlbench_tree - sh2 (tag: docker_sh2_perf) used for benches: ycsb_hash, ycsb_tree, cbench - sh3 (tag: docker_sh3_perf) used for benches: sysbench, tpcc - sh9 (tag: docker_perf_ssd) used for benches: linkbench_ssd - Changing gitlab-ci tag for performance docker images from 'perf' to 'deploy'. Closes #4868 (cherry picked from commit f262b64)
kyukhin
pushed a commit
that referenced
this issue
May 28, 2020
- Adding 2 servers (sh1, sh2) for performance testing. - Rebalance performance testing between servers: - sh1 (tag: docker_sh1_perf) used for benches: nosqlbench_hash, nosqlbench_tree - sh2 (tag: docker_sh2_perf) used for benches: ycsb_hash, ycsb_tree, cbench - sh3 (tag: docker_sh3_perf) used for benches: sysbench, tpcc - sh9 (tag: docker_perf_ssd) used for benches: linkbench_ssd - Changing gitlab-ci tag for performance docker images from 'perf' to 'deploy'. Closes #4868 (cherry picked from commit f262b64) Conflicts: .gitlab-ci.yml
kyukhin
pushed a commit
that referenced
this issue
May 28, 2020
- Adding 2 servers (sh1, sh2) for performance testing. - Rebalance performance testing between servers: - sh1 (tag: docker_sh1_perf) used for benches: nosqlbench_hash, nosqlbench_tree - sh2 (tag: docker_sh2_perf) used for benches: ycsb_hash, ycsb_tree, cbench - sh3 (tag: docker_sh3_perf) used for benches: sysbench, tpcc - sh9 (tag: docker_perf_ssd) used for benches: linkbench_ssd - Changing gitlab-ci tag for performance docker images from 'perf' to 'deploy'. Closes #4868 (cherry picked from commit f262b64)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently only one server is used for performance testing and single perf run takes 4 hours (and for testing one commit on all release branches it takes 16 hours). This is not suitable.
Need to parallelize perf testing between servers (each test(s) is running on its own machine).
The text was updated successfully, but these errors were encountered: