Operations and tuning for Cassandra involve:
1) Ensuring a good data model first before trying to optimize operations, as a bad model cannot be fixed by operations alone.
2) Sizing for latency and operations depends on factors like CPU, memory, disk type and replication factor, with SSDs offering much faster performance than mechanical disks.
3) Various tuning techniques are described like disabling access time, warming the buffer cache, using SSDs, adjusting read ahead and schedulers on SSDs, choosing appropriate compaction strategies, and Cassandra heap size settings.
5. Sizing for Operations
(C * Nodes * Cores) / Replication Factor = Ops/Second
C is a hardware constant!
• 3000 AWS Non-SSD!
• 4000 Commodity SAS Hardware!
• 12000 Commodity SSD Hardware
6. Sizing for Latency
• 30-130 microseconds in memory!
• 100 microseconds to 12 milliseconds for SSD!
• 9 milliseconds to 60 milliseconds for mechanical disks