×
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.
... some additional remarks to the discussion:
- cpu queuing in this context is: waiting for a free cpu, might be caused
by:
-- 100% used
-- too many concurrent threads for too few cpus
-- misconfiguration (to few activity levels in a subsystem)
- one JVM using multiple CPUs:
-- java uses native threads since 1.2 and it's up to the OS to dispatch a
thread to whatever cpu the OS wants
- one JVM or multiple JVMs:
-- good application design will use more than one JVM anyway. UI will need
one and the core business layer might use an appserver and maybe the
persistance layer another.
-- the database layer will run on as/400 in native jobs anyway (QZDASOINIT
and friends)
One interesting question to the OP would be, what software they are
migrating to and how the architecture is looking like. I have seen quite a
lot of bad designed java software, designed by programmers, thinking in RPG.
Second question would be, how the new hardware was calibrated, java for sure
would need much more processor ressources (CPU and memory) compared to rpg,
and it will make efficient use of it (in other words: many problems with
response times could be solved by hardware - that's very diffrent to RPG.
Dieter
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
