Thanks Peter for the extra detail.
I thought there may have been something more mysterious going on. But it sounds
like it was just the semantics of the term "use".
Cheers
Aaron
On 18/02/2011, at 9:25 PM, Peter Schuller wrote:
>> main argument for using mmap() instead of standard I/O is the f
> main argument for using mmap() instead of standard I/O is the fact
> that reading entails just touching memory - in the case of the memory
> being resident, you just read it - you don't even take a page fault
> (so no overhead in entering the kernel and doing a semi-context
> switch).
Oh and in
> Jonathan,
> When you get time could you please explain that a little more. Got a feeling
> I'm about to learn something :)
I'm not Jonathan, but: The operating system's virtual memory system
supports mapping files into a process' address space. This will "use"
virtual memory; i.e. address space.
Jonathan, When you get time could you please explain that a little more. Got a feeling I'm about to learn something :)ThanksAaronOn 18 Feb, 2011,at 01:36 PM, Jonathan Ellis wrote:Please note that this won't affect the actual memory in use, only how
the OS reports it.
On Thu, Feb 17, 2011 at 6:15
Please note that this won't affect the actual memory in use, only how
the OS reports it.
On Thu, Feb 17, 2011 at 6:15 PM, Aaron Morton wrote:
> Looks like you are using virtual memory for memmapped files. Change the
> disk_access_mode to standard if you want to reduce the overall memory
> usage.
Victor, I'm a bit confused here as we've now got two conversations in this thread. Can you please start a new thread about your memory problem, I'm not clear on the details. Please include...- cassandra version- JVM heap settings from bin/cassandra.in.sh or conf/cassandra-env.sh - disk_access_mode
Ruslan, Change your disk_access_mode standard to remove the virtual memory usage. Some info on JNAhttp://www.datastax.com/blog/whats-new-cassandra-066http://journal.paul.querna.org/articles/2010/11/11/enabling-jna-in-cassandra/AaronOn 18 Feb, 2011,at 09:00 AM, Aaron Morton wrote:What are you using
Already done. The disk access mode is standard in storage-conf.xml (I am
using 0.6.6 at the moment, I will upgrade to 0.7.x later). But this memory
consumption is a real issue.
2011/2/17 Aaron Morton
> Looks like you are using virtual memory for memmapped files. Change the
> disk_access_mode to
Looks like you are using virtual memory for memmapped files. Change the disk_access_mode to standard if you want to reduce the overall memory usage. AaronOn 18 Feb, 2011,at 09:34 AM, Victor Kabdebon wrote:Sorry I forgot to say that this is the partial result of : ps aux | grep cassandraBest regard
2011/2/17 Aaron Morton
> What are you using for disk_access_mode ?
>
I set config default: auto.
Have you tried reducing the JVM head size?
>
No i set default settings
> Have you added the Jna.jar file to lib/ ? This will allow Cassandra to lock
> the JVM memory.
>
> No, and what does this me
Sorry I forgot to say that this is the partial result of :
ps aux | grep cassandra
Best regards
2011/2/17 Victor Kabdebon
> Oh right but Cassandra doesn't really respect that, I thought there was
> another option to set that.
>
> Just for your information, I set xms and xmx very low with a smal
Oh right but Cassandra doesn't really respect that, I thought there was
another option to set that.
Just for your information, I set xms and xmx very low with a small amount of
data. I am waiting to be able to connect jconsole, I don't know why it is
not reachable at the moment. Here is my result
bin/cassandra.in.sh set Xms and Xmx in the JVM_OPTSAaronOn 18 Feb, 2011,at 09:10 AM, Victor Kabdebon wrote:Is it possible to change the maximum JVM heap memory use in 0.6.X ?2011/2/17 Aaron Morton
What are you using for disk_access_mode ?Have you tried reducing the JVM h
Is it possible to change the maximum JVM heap memory use in 0.6.X ?
2011/2/17 Aaron Morton
> What are you using for disk_access_mode ?
> Have you tried reducing the JVM head size?
> Have you added the Jna.jar file to lib/ ? This will allow Cassandra to lock
> the JVM memory.
>
>
> Aaron
>
>
> On
What are you using for disk_access_mode ?
Have you tried reducing the JVM head size?
Have you added the Jna.jar file to lib/ ? This will allow Cassandra to lock the
JVM memory.
Aaron
On 17/02/2011, at 9:20 PM, ruslan usifov wrote:
>
>
> 2011/2/16 Aaron Morton
> JVM heap memory is controlle
2011/2/16 Aaron Morton
> JVM heap memory is controlled by the settings in conf/Cassandra-env.sh
>
> Memory mapped files will use additional virtual memory, is controlled in
> conf/Cassandra.yaml disk_access_mode
>
>
And??? JVM memory heap in cassandra 0.7 is by default half of memory is
system in
JVM heap memory is controlled by the settings in conf/Cassandra-env.sh
Memory mapped files will use additional virtual memory, is controlled in
conf/Cassandra.yaml disk_access_mode
Aaron
On 17/02/2011, at 2:19 AM, ruslan usifov wrote:
> Hello
>
> Here is my output from ps aux:
>
> root
Hello
Here is my output from ps aux:
root 737 0.0 0.0 8940 804 ?S04:34 0:00 nimbus(hdb)
root 768 0.0 0.0 0 0 ?S04:34 0:00
[flush-202:0]
root 1368 43.1 70.5 8248976 5935852 ? Sl 04:45 297:47
/usr/local/jdk1.6.0_23/bin/java -ea -XX
18 matches
Mail list logo