Skip to content

Commit 672b97c

Browse files
authored
Update benchmnarking.md
1 parent 63e06cf commit 672b97c

File tree

1 file changed

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

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
2-
title: Cassendra Benchmarking
2+
title: Cassandra Benchmarking
33
weight: 6
44

55
### FIXED, DO NOT MODIFY
66
layout: learningpathall
77
---
88

9-
## Cassendra Benchmarking by Cassendra-Stress
9+
## Cassandra Benchmarking by Cassandra-Stress
1010
Cassandra benchmarking can be performed using the built-in `cassandra-stress` tool, which helps measure database performance under different workloads such as write, read, and mixed operations.
1111

12-
### Steps for Cassendra Benchmarking with Cassendra-Stress
12+
### Steps for Cassandra Benchmarking with Cassandra-Stress
1313
**Verify cassandra-stress Installation:**
1414

1515
Cassandra comes with a built-in tool called **cassandra-stress** that is used for testing performance. It is usually located in the `tools/bin/` folder of your Cassandra installation.
@@ -356,7 +356,7 @@ Results from the earlier run on the `c4a-standard-4` (4 vCPU, 16 GB memory) Arm6
356356
| Total GC Time | 0.0 s | 0.0 s |
357357
| Total Operation Time | 0:00:00 | 0:00:02 |
358358

359-
### Cassendra performance benchmarking notes
359+
### Cassandra performance benchmarking notes
360360
When examining the benchmark results, you will notice that on the Google Axion C4A Arm-based instances:
361361

362362
- 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.

0 commit comments

Comments
 (0)