[CASSANDRA-16338] STCS steady state load vs. steady state load with garbagecollect running performance test

• Type: Sub-task
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0
• Component/s: Test/benchmark
• Change Category: Quality Assurance
• Complexity: Normal
• Platform: All

Source Control Link

none

Test and Documentation Plan

Perf. Test Plan

1. Run data prepopulation
2. Run steady state load for X seconds as Phase 1.
3. Make one test case dependent change, e.g. triggering garbagecollect, altering table, etc., and continue the steady state load for Y seconds as Phase 2.
4. Compare the performance metrics beween Phase 1 and Phase 2.

The workload used in the test was generated from tlp-stress.

Steady state load Read : Write : Delete == 5 : 4 : 1, and the QPS was kept at 3K/s.

garbagecollect ran with 2 threads/jobs.

• Assignee: Yifan Cai
• Reporter: Yifan Cai

Authors

Yifan Cai

Reviewers

Marcus Eriksson

• Created: 12/Dec/20 00:31
• Updated: 10/Feb/21 09:21
• Resolved: 10/Feb/21 09:21

Description

The testing cluster should be pre-populated with ~200GB data in each node. Run the steady state workload to compare the read, write and compaction performance between before and during garbagecollect is running.