incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sridhar basam <sridhar.ba...@gmail.com>
Subject Re: using too much RAM
Date Thu, 14 Oct 2010 21:26:11 GMT
Yes, on linux atleast, lsof would show you that. lsof -d mem -p <pid>. You
can also look at /proc/<pid>/maps, again linux centric.

 Sridhar

On Thu, Oct 14, 2010 at 3:44 PM, B. Todd Burruss <bburruss@real.com> wrote:

>  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:
>>
>>> 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 the config. is there a way to verify this via JMX? (or
>>> some other way)
>>>
>> There is a log message at startup which will tell you the DiskAccessMode
>> and IndexAccessMode in use. It looks like..
>>
>> INFO 16:46:06,875 DiskAccessMode 'auto' determined to be mmap,
>> indexAccessMode is mmap
>>
>> =Rob
>>
>>


-- 
Sridhar

Mime
View raw message