You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/managed-instance-apache-cassandra/best-practice-performance.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -226,7 +226,7 @@ This indicates a problem in the data model. Here is a [stack overflow article](h
226
226
227
227
## Specialized optimizations
228
228
### Compression
229
-
Cassandra alows the selection of an appropriate compression algortihm when a table is created (see [Compression](https://cassandra.apache.org/doc/latest/cassandra/operating/compression.html) The default is LZ4 which is excellent
229
+
Cassandra allows the selection of an appropriate compression algortithm when a table is created (see [Compression](https://cassandra.apache.org/doc/latest/cassandra/operating/compression.html)) The default is LZ4 which is excellent
230
230
for throughput and CPU but consumes more space on disk. Using Zstd (Cassandra 4.0 and up) saves about ~12% space with
0 commit comments