smiklosovic commented on code in PR #4000:
URL: https://github.com/apache/cassandra/pull/4000#discussion_r2009716888
##########
doc/modules/cassandra/pages/architecture/storage-engine.adoc:
##########
@@ -1,12 +1,12 @@
= Storage Engine
-The {Cassandra} storage engine is optimized for high performance,
write-oriented workloads. The architecture is based on Log Structured Merge
(LSM) trees, which utilize an append-only approach instead of the traditional
relational database design with B-trees. This creates a write path free of read
lookups and bottlenecks.
+The Cassandra storage engine is optimized for high performance, write-oriented
workloads. The architecture is based on Log Structured Merge (LSM) trees,
which utilize an append-only approach instead of the traditional relational
database design with B-trees. This creates a write path free of read lookups
and bottlenecks.
While the write path is highly optimized, it comes with tradeoffs in terms of
read performance and write amplification. To enhance read operations, Cassandra
uses Bloom filters when accessing data from stables. Bloom filters are
remarkably efficient, leading to generally well-balanced performance for both
reads and writes.
-Compaction is a necessary background activity required by the ‘merge’ phase of
Log Structured Merge trees. Compaction creates write amplification when several
small SSTables on disk are read, merged, updates and deletes processed, and a
new ssstable is re-written. Every write of data in Cassandra is re-written
multiple times, known as write amplification, and this adds background I/O to
the database workload.
+Compaction is a necessary background activity required by the ‘merge’ phase of
Log Structured Merge trees. Compaction creates write amplification when several
small SSTables on disk are read, merged, updates and deletes processed, and a
new sstable is re-written. Every write of data in Cassandra is re-written
multiple times, known as write amplification, and this adds background I/O to
the database workload.
Review Comment:
it is `SSTable`
##########
doc/modules/cassandra/pages/architecture/storage-engine.adoc:
##########
@@ -18,19 +18,19 @@ The sequence of the steps in the write path:
[[commit-log]]
== Logging writes to commit logs
-When a write occurs, {cassandra} writes the data to a local append-only
(https://cassandra.apache.org/_/glossary.html#commit-log)[commit log] on disk.
-This action provides
xref:cassandra:managing/configuration/cass_yaml_file.adoc[configurable
durability] by logging every write made to a {cassandra} node.
+When a write operation takes place, Cassandra records the data in a local
append-only https://cassandra.apache.org/_/glossary.html#commit-log[commit log]
on disk.
Review Comment:
@arrapraveen221 cant be this also referenced somehow differently as below
line? This will not render correctly if it is previewed locally.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: pr-unsubscr...@cassandra.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscr...@cassandra.apache.org
For additional commands, e-mail: pr-h...@cassandra.apache.org
