On 10/14/10 12:44 PM, B. Todd Burruss wrote:
> >> INFO 16:46:06,875 DiskAccessMode 'auto' determined to be mmap,
>> indexAccessMode is mmap
thx, it does say that in the log, but that is probably just a reflection
of whatever is read from cassandra.yaml.
Having read the relevant code, the log me
Yes, on linux atleast, lsof would show you that. lsof -d mem -p . You
can also look at /proc//maps, again linux centric.
Sridhar
On Thu, Oct 14, 2010 at 3:44 PM, B. Todd Burruss wrote:
> thx, it does say that in the log, but that is probably just a reflection
> of whatever is read from cassan
thx, it does say that in the log, but that is probably just a
reflection of whatever is read from cassandra.yaml.
i am wondering if some unix tool can tell me if my process is mmap'ing
files. maybe lsof?
On 10/14/2010 12:07 PM, Rob Coli wrote:
On 10/14/10 10:59 AM, B. Todd Burruss wrote:
On 10/14/10 10:59 AM, B. Todd Burruss wrote:
0.7.0-beta2
top is reporting my cassandra process as using 11g. i have set
"disk_access_mode: standard" and Xmx8G (verified via JMX)
i have only noticed using more RAM than Xmx when using mmap i/o. this
leads me to believe that disk_access_mode was n
what does it report when you do allow mmap'd i/o to be used? (which
you should always do anyway if you care about performance.)
On Thu, Oct 14, 2010 at 12:59 PM, B. Todd Burruss wrote:
> 0.7.0-beta2
>
> top is reporting my cassandra process as using 11g. i have set
> "disk_access_mode: standar
0.7.0-beta2
top is reporting my cassandra process as using 11g. i have set
"disk_access_mode: standard" and Xmx8G (verified via JMX)
i have only noticed using more RAM than Xmx when using mmap i/o. this
leads me to believe that disk_access_mode was not set properly, even
though it is in t
