× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. June 2007

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.)



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.