Re: Tuning a column family for archival

2011-08-11 Thread Jonathan Ellis
No. He's saying that one of the points of mmaping the data files is that the OS is free to only keep files that are actually used, in the page cache. Since this data is backed by an actual file swap is not involved. On Thu, Aug 11, 2011 at 12:59 PM, Jason Baker wrote: > On Thu, Aug 11, 2011 at

Re: Tuning a column family for archival

2011-08-11 Thread Jason Baker
On Thu, Aug 11, 2011 at 6:14 AM, Edward Capriolo wrote: > > In many regards Cassandra automatically does the correct thing. Other then > the costs of the bloom filters for the table size being in ram, if you never > read or write to those sstables and you are not reusing the row key, the OS > will

Re: Tuning a column family for archival

2011-08-11 Thread Edward Capriolo
On Thu, Aug 11, 2011 at 12:07 AM, aaron morton wrote: > There's not much to do other than turn off the caches (which you have done) > and leave it alone. > > If you want to poke around perhaps look at the compaction settings (from > CLI help): > > - max_compaction_threshold: The maximum number of

Re: Tuning a column family for archival

2011-08-10 Thread aaron morton
There's not much to do other than turn off the caches (which you have done) and leave it alone. If you want to poke around perhaps look at the compaction settings (from CLI help): - max_compaction_threshold: The maximum number of SSTables allowed before a minor compaction is forced. Default is

Tuning a column family for archival

2011-08-10 Thread Jason Baker
I have a column family that I'm using to archive records. They're mostly kept around for historical purposes. Aside from that, they're mostly considered deleted. It's probably going to be very rare that anyone reads from this table *ever*. I don't really even write to it that much. Does anyone