dev@glassfish.java.net

Re: Changes to VM tuning.

From: Peter Williams <Pete.Williams_at_Sun.COM>
Date: Mon, 23 Jul 2007 14:42:56 -0700

My main workstation is a dual core CPU + 2GB of RAM. Since I'm running
Solaris 10, that means the JVM will soon default to -server.

But since I'm using glassfish from the perspective of a developer
(start/stop time very relevant, overall server throughput irrelevant),
this change will lower the "out of the box" performance of the server.

Why not keep the -client switch, but control it's insertion (or not) to
the installed profile -- install for "deployment", "runtime" or whatever
we call it would get -server and developer profiles would get "-client"?

-Peter

Binod wrote:
>
> Hi everyone,
>
> Heads up regarding some changes to default JVM options for glassfish.
> I am planning to do the check-in in next couple of days.
>
> We are removing the default -client option from the developer profile
> domain.xml. That means that in server class machines glassfish will be
> starting with -server VM (tuned for runtime performance and not startup).
>
> When VM is server, QuickStartup also will be switched off as the
> intention is to tune for runtime performance in server-class machines
> and not startup.
>
> In client-class machines the current behaviour will continue as the JDK
> will pick -client as the default VM.
>
> thanks,
> Binod.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>