|
We are not stuck with a particular Java release, but we develop against 1.4 to be able to run on whatever JVM the client has installed.We develop against 1.4
If you're not stuck with a particular Java release ( like WebSphere
imposes, ) IMO you should at least go to 1.5 to pick up the performance and
GC benefits without changing any code. And that's for any system, not just an AS/400.
Sure, but we are still learning how the various parts of OS/400 interact and Java apps are different because they have a very large memory footprint. To avoid swapping it in we have found that it helps reserving a large chunk of memory AFTER performance degradation has been found.I have understood it is enough to "just" stow the Java stuff away in a
subsystem with 1Gb RAM for itself.
No offense, but that makes no sense to me except for the particular case
where a particular app happens to fit. Otherwise, you're either throwing
away memory that could be used in other areas or not giving Java enough.
Habits are individual. It was just a suggestion.I notice you toppost while copying in the original text
I just prefer not to have to search through a lot of intermingled pieces
somewhere throughout the original message, which I leave intact, and try to
do the same favor for others.
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.