Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Oleg Piskunov" <o.piskunov@tarantool.org>
To: tarantool-patches@dev.tarantool.org
Subject: [Tarantool-patches] [PATCH v1] gitlab-ci: add TPC-H perf testing
Date: Mon, 15 Jun 2020 13:54:46 +0300	[thread overview]
Message-ID: <1592218486.117480442@f304.i.mail.ru> (raw)

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


- Adding TPC-H into perf testing pipeline
- Using sh2 server for TPC-H testing
- Keep raw SQLite results into artifacts
 
Closes #5010
---
 
Github:  https://github.com/tarantool/tarantool/tree/opiskunov/gh-5010-add-tpch-perf

 .gitlab-ci.yml | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 65b2fb1..9df2a17 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -39,6 +39,7 @@ variables:
   variables: &perf_vars_definition
     IMAGE_PERF: "${CI_REGISTRY}/${CI_PROJECT_PATH}/perf/ubuntu-bionic:perf_master"
     IMAGE_PERF_BUILT: "${CI_REGISTRY}/${CI_PROJECT_PATH}/perf_tmp/ubuntu-bionic:perf_${CI_COMMIT_SHORT_SHA}"
+    IMAGE_PERF_TPCH_BUILT: "${CI_REGISTRY}/${CI_PROJECT_PATH}/perf_tmp_tpch/ubuntu-
 
bionic:perf_${CI_COMMIT_SHORT_SHA}"
 .docker_test_template: &docker_test_definition
   image: "${CI_REGISTRY}/${CI_PROJECT_PATH}/testing/debian-stretch:latest"
@@ -211,6 +212,21 @@ perf_bootstrap:
 
 # Testing part
 
+perf_tpch:
+  <<: *perf_docker_test_definition
+  image: ${IMAGE_PERF_TPCH_BUILT}
+  tags:
+    - docker_sh2_perf
+  artifacts:
+    when: always
+    paths:
+      - "bench-*.csv"
+      - "*_t_version.txt"
+      - "*_result.txt"
+  variables:
+    <<: *perf_vars_definition
+    BENCH: 'tpch'
+
 perf_sysbench:
   <<: *perf_docker_test_definition
   tags:
--
1.8.3.1
 

[-- Attachment #2: Type: text/html, Size: 2028 bytes --]

                 reply	other threads:[~2020-06-15 12:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1592218486.117480442@f304.i.mail.ru \
    --to=o.piskunov@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v1] gitlab-ci: add TPC-H 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