Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "CassandraHardware" page has been changed by JonathanEllis. http://wiki.apache.org/cassandra/CassandraHardware?action=diff&rev1=2&rev2=3 -------------------------------------------------- === Memory === - The most recently written data resides in memory tables (aka [[MemtableThresholds|memtables]]), but older data that has been flushed to disk can be kept in the OS's file-system cache. In other words, ''the more memory, the better'', with 1GB being the minimum recommended. + The most recently written data resides in memory tables (aka [[MemtableThresholds|memtables]]), but older data that has been flushed to disk can be kept in the OS's file-system cache. In other words, ''the more memory, the better'', with 1GB being the minimum recommended in a virtualized environment. With dedicated hardware there is no reason to use less than 4GB, and at the high end, you see clusters with 16 or 32 GB. === CPU === Many workloads will actually be CPU-bound in Cassandra before being memory-bound. Cassandra is highly concurrent and will make good use of however many cores you can give it. For high-end clusters, quad- or 8-core boxes are good. If you're running on virtualized machines, consider using a provider such as Rackspace Cloud Servers that allows CPU bursting. - === Disk === The short answer here is, ''at least 2 disks'', one to keep your `CommitLogDirectory` on, the other to use in `DataFileDirectories`. The exact answer though depends a lot on your usage so it's important to understand what is going on here.
