I agree.
Major GC always means "pause" in application execution. This will
definitely hurt overall throughput & latency.
I think the goals of optimizing GC is to
1. reduce # of Major GC as much as possible;
2. reduce frequency of Minor GC as much as possible;
In order to achieve Goal #1, appli
Interesting settings Sam,
I'm curious about this one:
"-XX:MaxTenuringThreshold=0" ; Makes the full NewSize available to every
NewGC
; cycle, and reduces the pause time by not
; evaluating tenured objects. Technically,
For those deploying to Oracle Java 7, an updated GC reference (including
valid combinations) is available at
http://www.fasterj.com/articles/oraclecollectors1.shtml.
Regards
Edward
On Tuesday, July 3, 2012 5:48:15 AM UTC-4, Niels van Klaveren wrote:
>
> I haven't got much experience with large
Hi Bruce,
at the bottom of this file you can see the options we use in Overtone to try
and reduce latency (i.e. we're not so worried about throughput, but are trying
to minimise the occurrence of long GC pauses)
https://github.com/overtone/overtone/blob/master/project.clj
Sam
---
http://sam.a
I haven't got much experience with large scale Clojure environments, but I
do know something from managing a lot of JVM production environments. The
biggest lesson is: All applications behave differently, usually more so in
type of application than JVM language used. No hard and fast rules can b
