Re: Estimation of memtable size are wrong

2012-03-26 Thread aaron morton
> Yes i noticed that. Its not too often, about 1 times per week. The assumption would be that the workload stabilises over time. > INFO [MemoryMeter:1] 2012-03-23 00:00:18,407 Memtable.java (line 186) > CFS(Keyspace='whois', ColumnFamily='ipbans') liveRatio is 64.0 (just-counted > was 16.3546327

Re: Estimation of memtable size are wrong

2012-03-26 Thread Radim Kolar
Dne 26.3.2012 0:36, aaron morton napsal(a): 1. its not possible to run them more often? There should be some limit - run live/serialized calculation at least once per hour. They took just few seconds. The live ratio is updated every time the operation count (since startup) for the CF doubles.

Re: Estimation of memtable size are wrong

2012-03-25 Thread aaron morton
> 1. its not possible to run them more often? There should be some limit - run > live/serialized calculation at least once per hour. They took just few > seconds. The live ratio is updated every time the operation count (since startup) for the CF doubles. > 2. Why not use data from FlusherWrit

Estimation of memtable size are wrong

2012-03-23 Thread Radim Kolar
I wonder why are memtable estimations so bad. 1. its not possible to run them more often? There should be some limit - run live/serialized calculation at least once per hour. They took just few seconds. 2. Why not use data from FlusherWriter to update estimations? Flusher knows number of ops a