From: "Oleg Piskunov" <o.piskunov@tarantool.org> To: tarantool-patches <tarantool-patches@dev.tarantool.org> Subject: [Tarantool-patches] [PATCH v1] gitlab-ci: parallelize perf testing Date: Fri, 08 May 2020 11:58:04 +0300 [thread overview] Message-ID: <1588928284.299581840@f558.i.mail.ru> (raw) [-- Attachment #1: Type: text/plain, Size: 2410 bytes --] - 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 --- Github: https://github.com/tarantool/tarantool/tree/opiskunov/gh-4868-parallel-perf Issue: https://github.com/tarantool/tarantool/issues/4868 .gitlab-ci.yml | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index ae2afce..897f657 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -91,8 +91,6 @@ variables: <<: *perf_only_definition image: ${IMAGE_PERF_BUILT} stage: perf - tags: - - docker_perf artifacts: when: always paths: @@ -195,7 +193,7 @@ perf_bootstrap: <<: *perf_only_definition stage: test tags: - - perf + - deploy script: - ${GITLAB_MAKE} perf_prepare @@ -203,18 +201,24 @@ perf_bootstrap: perf_sysbench: <<: *perf_docker_test_definition + tags: + - docker_perf variables: <<: *perf_vars_definition BENCH: 'sysbench' perf_tpcc: <<: *perf_docker_test_definition + tags: + - docker_perf variables: <<: *perf_vars_definition BENCH: 'tpcc' perf_ycsb_hash: <<: *perf_docker_test_definition + tags: + - docker_sh2_perf variables: <<: *perf_vars_definition BENCH: 'ycsb' @@ -222,6 +226,8 @@ perf_ycsb_hash: perf_ycsb_tree: <<: *perf_docker_test_definition + tags: + - docker_sh2_perf variables: <<: *perf_vars_definition BENCH: 'ycsb' @@ -229,6 +235,8 @@ perf_ycsb_tree: perf_nosqlbench_hash: <<: *perf_docker_test_definition + tags: + - docker_sh1_perf variables: <<: *perf_vars_definition BENCH: 'nosqlbench' @@ -236,6 +244,8 @@ perf_nosqlbench_hash: perf_nosqlbench_tree: <<: *perf_docker_test_definition + tags: + - docker_sh1_perf variables: <<: *perf_vars_definition BENCH: 'nosqlbench' @@ -243,6 +253,8 @@ perf_nosqlbench_tree: perf_cbench: <<: *perf_docker_test_definition + tags: + - docker_sh2_perf variables: <<: *perf_vars_definition BENCH: 'cbench' -- 1.8.3.1 [-- Attachment #2: Type: text/html, Size: 3692 bytes --]
next reply other threads:[~2020-05-08 8:58 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-08 8:58 Oleg Piskunov [this message] 2020-05-13 18:48 ` Alexander V. Tikhonov 2020-05-15 7:43 ` Oleg Piskunov 2020-05-14 8:29 ` Sergey Bronnikov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1588928284.299581840@f558.i.mail.ru \ --to=o.piskunov@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v1] gitlab-ci: parallelize perf testing' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox