Skip to content

Commit 193a662

Browse files
Merge pull request #2468 from DougAnsonAustinTX/benchmark_updates
small edit of benchmark results
2 parents 44cc20f + 87ab4f5 commit 193a662

File tree

1 file changed

+7
-28
lines changed
  • content/learning-paths/servers-and-cloud-computing/cassandra-on-gcp

1 file changed

+7
-28
lines changed

content/learning-paths/servers-and-cloud-computing/cassandra-on-gcp/benchmnarking.md

Lines changed: 7 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -335,30 +335,8 @@ END
335335
- **GC metrics (Garbage Collection):** Shows whether JVM garbage collection paused Cassandra during the test.
336336
- **Total operation time:** The total wall-clock time taken to run the benchmark.
337337

338-
### Benchmark summary on x86_64
339-
To compare the benchmark results, the following results were collected by running the same benchmark on a `x86 - c4-standard-4` (4 vCPUs, 15 GB Memory) x86_64 VM in GCP, running SUSE:
340-
341-
| Metric | Write Test | Read Test |
342-
|----------------------------|----------------------|----------------------|
343-
| Operation Rate (op/s) | 4,922 | 4,349 |
344-
| Partition Rate (pk/s) | 4,922 | 4,349 |
345-
| Row Rate (row/s) | 4,922 | 4,349 |
346-
| Latency Mean | 8.4 ms | 8.0 ms |
347-
| Latency Median | 5.9 ms | 6.6 ms |
348-
| Latency 95th Percentile | 22.9 ms | 18.7 ms |
349-
| Latency 99th Percentile | 40.4 ms | 28.9 ms |
350-
| Latency 99.9th Percentile | 75.0 ms | 48.9 ms |
351-
| Latency Max | 175.2 ms | 84.0 ms |
352-
| Total Partitions | 10,000 | 10,000 |
353-
| Total Errors | 0 | 0 |
354-
| Total GC Count | 0 | 0 |
355-
| Total GC Memory | 0 B | 0 B |
356-
| Total GC Time | 0.0 s | 0.0 s |
357-
| Total Operation Time | 0:00:02 | 0:00:02 |
358-
359-
360338
### Benchmark summary on Arm64
361-
Results from the earlier run on the `c4a-standard-4` (4 vCPU, 16 GB memory) Arm64 VM in GCP (SUSE):
339+
Results from the earlier run on the `c4a-standard-4` (4 vCPU, 16 GB memory) Arm64 VM in GCP (SuSE shown, Ubuntu results were very similar):
362340

363341
| Metric | Write Test | Read Test |
364342
|----------------------------|----------------------|----------------------|
@@ -378,11 +356,12 @@ Results from the earlier run on the `c4a-standard-4` (4 vCPU, 16 GB memory) Arm6
378356
| Total GC Time | 0.0 s | 0.0 s |
379357
| Total Operation Time | 0:00:00 | 0:00:02 |
380358

381-
### Cassendra performance benchmarking comparison on Arm64 and x86_64
382-
When you compare the benchmarking results, you will notice that on the Google Axion C4A Arm-based instances:
359+
### Cassendra performance benchmarking notes
360+
When examining the benchmark results, you will notice that on the Google Axion C4A Arm-based instances:
383361

384362
- The write operations achieved a high throughput of **10,690 op/s**, while read operations reached **4,962 op/s** on the `c4a-standard-4` Arm64 VM.
385-
- Latency for writes was lower (mean: **3.7 ms**) compared to reads (mean: **6.3 ms**), indicating faster write processing on this setup.
386-
- The 95th and 99th percentile latencies show consistent performance, with writes significantly faster than reads (write 95th: **9.5 ms** vs read 95th: **17.4 ms**).
363+
- Latency for writes was very low (mean: **3.7 ms**) compared to reads (mean: **6.3 ms**), indicating fast write processing on this Arm64 VM.
364+
- The 95th and 99th percentile latencies show consistent performance, with writes significantly faster than reads.
387365
- There were no errors or GC overhead, confirming stable and reliable benchmarking results.
388-
- Overall, the Arm64 VM provides efficient and predictable performance, making it suitable for high-throughput Cassandra workloads.
366+
367+
Overall, the Arm64 VM provides efficient and predictable performance, making it suitable for high-throughput Cassandra workloads.

0 commit comments

Comments
 (0)