Hey,
Your Java application is a standalone application or does it run on top of an
application
server ?
Couple of things to consider here:
- are you running on 32 or 64 bit JVM ?
- which version of Java are you using: 5 or 6 ?
- you are saying that your application should reduce to maximum th
First, you really need to increase the heap size. You have 16GB so take
advantage of it. Then Concurrent Mark Sweep may actually work.
You didn't mention what JVM you are using, it matters.
I did a presentation recently on Java GC that you might be interested,
http://docs.google.com/Present
BTW, would Real-Time Java be useful in this kind of environment??
Rayson
On Dec 29, 2007 1:30 PM, adrian cockcroft <[EMAIL PROTECTED]> wrote:
> Concurrent GC is likely to use a lot more RAM than stop and sweep, so
> increase your heap to 3-4GB and try the concurrent collector again. If
> that ru
Concurrent GC is likely to use a lot more RAM than stop and sweep, so
increase your heap to 3-4GB and try the concurrent collector again. If
that runs out of RAM, go to 64bit Java and keep increasing it, you
have 16GB available in the machine...
Peter Johnson of Unisys has a great workshop on tuni
On Sat, Dec 29, 2007 at 08:44:31AM -0800, Sambasiva Rao Andaluri wrote:
> Hi,
> We are developing a Java application that consumes real time equity market
> data. The application is run on a 2 CPU dual core Opteron box (4 cores with
> each 2593Mhz) with about 16GB RAM. The JVM is run in Server mo
