At 12:49 PM 7/25/2001, Duffey, Kevin wrote:
>I am interested in your two fixes. Have you (or anyone) noticed that Orion
>actually requires 175MB of RAM?

I think it's mainly our Servlet that uses this up.  I think it depends on 
how many servlets you load.

>  Is there a definite need to use both memory
>switches, or perhaps one over the other? What is the use and/or meaning of
>each switch?

-Xms = minimum amount of memory the JVM will use
-Xmx = mazimum amount of memory the JVM will use

>  What I find funny is I just installed JDK 1.3.1 and noticed the
>/server, /classic and /hotspot dirs under bin which contain the jvm.dll that
>Windows uses. I was actually going to post an email to this and JSP interest
>list asking what the benefits and differences are between the 3 jvms.

BIG benefits, just try it.

>  I
>haven't been able to find anything on the sun site that details how they are
>different. Can you fill me in if you know, what makes the server jvm better?

 From what I understand, it uses memory and processors more efficiently, 
more driven for background apps rather than a client JVM driven with 
foreground apps in mind.

>Is it better overall for all use (other than client-side SWING apps)? I
>thought the hotspot was the best because of the inline JIT that converts
>code to native..and thus should speed it up greatly. Is the server better
>just for production use, or for anyone running Orion locally for web
>development as well? Ideally, I would think we want our development, qa,
>staging and live servers to all run the same JVM to make sure we all see any
>problems that arise.

I use it for everything here now.  No harm, just benefits, you just gotta 
have the RAM.

R


Robert S. Sfeir
Director of Software Development
PERCEPTICON corporation,
        in Joint Venture With JTransit
San Francisco, CA 94123
pw - http://www.percepticon.com/
jw - http://jtransit.com
e- [EMAIL PROTECTED]


Reply via email to