RE: Overhead/downsides to JVM in each job (was: JVM properties -angst)

No, I wouldn't want to do it. First, starting the JVM takes a

significant

amount of time. And even though subsequent calls are much faster, that
performance stills depends on how many JVMs are running, and in today's
i5/OS implementation, a JVM cannot be shared between two jobs. Every

job

that runs Java must have its own private JVM.

Those were my assumptions, but I wanted to validate them. In our case
it's not used regularly, but it would still be annoying to wait for the
JVM startup. Add to that the concern about JVM versions and I feel we
made the right decision. Seems to me that Java (on any platform) is a
server-side tool, not a client-side one. JVM startup on windows isn't
the fastest thing in the world either. <G>

-Walden

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)