Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Oleg Piskunov" <o.piskunov@tarantool.org>
To: tarantool-patches@dev.tarantool.org
Cc: "Alexander Turenko" <alexander.turenko@tarantool.org>
Subject: [Tarantool-patches] [PATCH v2] gitlab-ci: parallelize perf testing
Date: Sat, 16 May 2020 09:56:22 +0300	[thread overview]
Message-ID: <1589612182.887817168@f503.i.mail.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 2647 bytes --]


 
- 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
---
 
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 c7f58b9..fc214ef 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:
@@ -191,7 +189,7 @@ perf_bootstrap:
   <<: *perf_only_definition
   stage: test
   tags:
-    - perf
+    - deploy
   script:
     - ${GITLAB_MAKE} perf_prepare
 
@@ -199,18 +197,24 @@ perf_bootstrap:
 
 perf_sysbench:
   <<: *perf_docker_test_definition
+  tags:
+    - docker_sh3_perf
   variables:
     <<: *perf_vars_definition
     BENCH: 'sysbench'
 
 perf_tpcc:
   <<: *perf_docker_test_definition
+  tags:
+    - docker_sh3_perf
   variables:
     <<: *perf_vars_definition
     BENCH: 'tpcc'
 
 perf_ycsb_hash:
   <<: *perf_docker_test_definition
+  tags:
+    - docker_sh2_perf
   variables:
     <<: *perf_vars_definition
     BENCH: 'ycsb'
@@ -218,6 +222,8 @@ perf_ycsb_hash:
 
 perf_ycsb_tree:
   <<: *perf_docker_test_definition
+  tags:
+    - docker_sh2_perf
   variables:
     <<: *perf_vars_definition
     BENCH: 'ycsb'
@@ -225,6 +231,8 @@ perf_ycsb_tree:
 
 perf_nosqlbench_hash:
   <<: *perf_docker_test_definition
+  tags:
+    - docker_sh1_perf
   variables:
     <<: *perf_vars_definition
     BENCH: 'nosqlbench'
@@ -232,6 +240,8 @@ perf_nosqlbench_hash:
 
 perf_nosqlbench_tree:
   <<: *perf_docker_test_definition
+  tags:
+    - docker_sh1_perf
   variables:
     <<: *perf_vars_definition
     BENCH: 'nosqlbench'
@@ -239,6 +249,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: 4062 bytes --]

             reply	other threads:[~2020-05-16  6:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16  6:56 Oleg Piskunov [this message]
2020-05-17 12:34 ` Alexander V. Tikhonov
2020-05-18  9:14 ` Sergey Bronnikov
2020-05-28  7:40 ` Kirill Yukhin

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=1589612182.887817168@f503.i.mail.ru \
    --to=o.piskunov@tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v2] 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