Got it, thanks
2010/4/13 Peter Schüller :
>> FYI, G1 has been in 1.6 since u14.
>
> Yes, but (last time I checked) in a considerably older form. The JDK
> 1.7 one is more mature.
>
> --
> / Peter Schuller aka scode
>
> FYI, G1 has been in 1.6 since u14.
Yes, but (last time I checked) in a considerably older form. The JDK
1.7 one is more mature.
--
/ Peter Schuller aka scode
FYI, G1 has been in 1.6 since u14.
2010/4/13 Peter Schüller :
>> I'm working on getting our latency as consistent as possible, and the gc
>> likes to kick off 60+ms periods of unavailability for a node, which for my
>> application leads to a reasonable number of timed out requests. Outside of
>
> I'm working on getting our latency as consistent as possible, and the gc
> likes to kick off 60+ms periods of unavailability for a node, which for my
> application leads to a reasonable number of timed out requests. Outside of
> the gc event, we get good responses.
>
> I'm happy with reduced t
Which version of the JVM are you using? Recent builds (u18, u19) have
significantly improved GC.
On Tue, Apr 13, 2010 at 3:51 PM, Daniel Kluesing wrote:
> Has anyone done any tuning on the jvm gc options or are the options included
> in bin/cassandra.in.sh basically the best choice?
&
Has anyone done any tuning on the jvm gc options or are the options included in
bin/cassandra.in.sh basically the best choice?
I'm working on getting our latency as consistent as possible, and the gc likes
to kick off 60+ms periods of unavailability for a node, which for my
application
