AggressiveOpts, if i remember correctly, uses options that are not
documented but will probably make into a future release of the JVM.
cassandra used it once upon a time. probably should take it out, but
things work just fine for me now ;)
On Tue, 2010-07-27 at 01:48 -0700, Dathan Pattishall wr
woot thnx, lots of knobs to play with!
On Tue, Jul 27, 2010 at 12:16 AM, Peter Schuller <
peter.schul...@infidyne.com> wrote:
> > @Todd, I noticed some new ops in your cassandra.in.sh. Is there any
> > documentation on what these ops are, and what they do?
> >
> > For instance AggressiveOpts, etc
soon because that is under consideration.
/Justus
-Ursprungligt meddelande-
Från: B. Todd Burruss [mailto:bburr...@real.com]
Skickat: den 27 juli 2010 01:33
Till: user@cassandra.apache.org
Ämne: Re: Key Caching
i run cassandra with a 30gb heap on machines with 48gb total with good
> @Todd, I noticed some new ops in your cassandra.in.sh. Is there any
> documentation on what these ops are, and what they do?
>
> For instance AggressiveOpts, etc.
A fairly complete list is here:
http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp
--
/ Peter Schuller
@Todd, I noticed some new ops in your cassandra.in.sh. Is there any
documentation on what these ops are, and what they do?
For instance AggressiveOpts, etc.
On Mon, Jul 26, 2010 at 4:33 PM, B. Todd Burruss wrote:
> i run cassandra with a 30gb heap on machines with 48gb total with good
> resul
i run cassandra with a 30gb heap on machines with 48gb total with good
results. i don't use more just because i want to leave some for the OS
to cache disk pages, etc. i did have the problem a couple of times with
GC doing a full stop on the JVM because it couldn't keep up. my
understanding of t
> If the cache is stored in the heap, how big can the heap be made
> realistically on a 24gb ram machine? I am a java newbie but I have read
> concerns with going over 8gb for the heap as the GC can be too painful/take
> too long. I already have seen timeout issues (node is dead errors) under
> loa
If the cache is stored in the heap, how big can the heap be made
realistically on a 24gb ram machine? I am a java newbie but I have read
concerns with going over 8gb for the heap as the GC can be too painful/take
too long. I already have seen timeout issues (node is dead errors) under
load during G
(the following are best-effort answers resulting from taking the
opportunity to look at the source; i may be missing something)
> I am trying to use the key cache, and I had some basic questions as to how
> it works. There seem to be settings based on % and total count, but not on
> total cache si
I am trying to use the key cache, and I had some basic questions as to how
it works. There seem to be settings based on % and total count, but not on
total cache size like most caching mechanisms. Is the cache stored in the
jvm heap or somewhere else? We have 24gb RAM nodes with a 8gb jvm heap size
10 matches
Mail list logo
