> > Though in general I would say that it is worth considering. In > particular if you have certain data that is accessed a lot more > frequently than other data (especially if the "other data" is large), > the improved cache locality of keeping the frequently accessed data > separate can be high (assuming greater-than-RAM data sets). Another > concern might be if you have some parts that are constantly updated or > deleted, while some other part that is mostly append-only. The > compaction needs of the frequently overwriting/removed data may be > higher, which may also be a reason to separate it out. >
Excellent point, Peter. Thanks for adding that. Taking into consideration effective caching and keeping the number of rows an SSTable is split across are both fairly advanced performance topics, but certainly worth considering once you have a solid data model (and a lot of data :). - Tyler
