We are at V5R4 and have been using WAS for EGL. We were very slow to begin with at 64 bit. Talking with IBM support it was suggested we throw more memory in and put WAS in its own pool. I think we associated 1GB to the pool. It helped a little but was still a poor performer. It was not until we installed the 32 bit version that it woke up. We have partner company that rewrote a large application in java by seasoned programmers and they have had poor performance as well until they went to 32 bit.

Thorbjørn Ravn Andersen wrote:
Gregg Willow skrev den 05-05-2008 23:02:
Thorbjørn,

Are you using the 32 bit version of WAS? The 64 bit version is very slow.

I am developing on V5R3 where I only have the Classic JVM (64 bit), but with the jitc it can be brought to run quite ok if you know what you do. We do not currently run inside WebSphere but use an embedded Jetty instead. It gives acceptable performance after being allowed to warm up.

Is your experience of slowness perhaps related to optimizing to a level or having insufficient memory?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.