Examine performance under concurrency

Open
#2 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
shell

Research direction

No files or tests are named. Start by locating the benchmark entry points and warehouse configuration, then measure six or more concurrent queries against Redshift, BigQuery, and Snowflake; done means the performance differences and Redshift query-queue behavior are captured in reproducible results.

Written by the indexing model from the issue text.

Description

Realistic scenarios frequently involve multiple analysts using the same db at the same time. Examine performance with 6+ queries going at once. Under Redshift's default options this will likely result in issues (http://docs.aws.amazon.com/redshift/latest/dg/cm-c-defining-query-queues.html) that shouldn't be experienced by BigQuery and experienced to a lesser extent on Snowflake.

Dominant language
Shell
Stars
171
Forks
41
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fivetran/benchmark

All issues in fivetran/benchmark

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.