mirror of https://github.com/apache/cassandra
Merge branch 'cassandra-3.11' into cassandra-4.0
This commit is contained in:
commit
1929550fc0
|
|
@ -28,7 +28,7 @@ here, however, you’ll want to think not only from the customer
|
|||
perspective in terms of how the data is written, but also in terms of
|
||||
how the data will be queried by downstream use cases.
|
||||
|
||||
You natural tendency as might be to focus first on designing the tables
|
||||
Your natural tendency might be to focus first on designing the tables
|
||||
to store reservation and guest records, and only then start thinking
|
||||
about the queries that would access them. You may have felt a similar
|
||||
tension already when discussing the shopping queries before, thinking
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ image::data_modeling_hotel_relational.png[image]
|
|||
== Design Differences Between RDBMS and Cassandra
|
||||
|
||||
Let’s take a minute to highlight some of the key differences in doing
|
||||
ata modeling for Cassandra versus a relational database.
|
||||
data modeling for Cassandra versus a relational database.
|
||||
|
||||
=== No joins
|
||||
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ appropriate number of replicates, to ensure even token allocation.
|
|||
Read ahead is an operating system feature that attempts to keep as much
|
||||
data as possible loaded in the page cache.
|
||||
Spinning disks can have long seek times causing high latency, so additional
|
||||
throughout on reads using page cache can improve performance.
|
||||
throughput on reads using page cache can improve performance.
|
||||
By leveraging read ahead, the OS can pull additional data into memory without
|
||||
the cost of additional seeks.
|
||||
This method works well when the available RAM is greater than the size of the
|
||||
|
|
|
|||
Loading…
Reference in New Issue