RE: Servlet Load Times under WAS on an iSeries! -- JAVA400-L

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

Subject: RE: Servlet Load Times under WAS on an iSeries!
From: "David Morris" <dmorris@xxxxxxxxxxxxx>
Date: Thu, 13 Sep 2001 08:22:22 -0600
List-Archive: <http://archive.midrange.com/java400-l/>
List-Help: <mailto:java400-l-request@midrange.com?subject=help>
List-Id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-Post: <mailto:java400-l@midrange.com>
List-Subscribe: <http://lists.midrange.com/cgi-bin/listinfo/java400-l>,<mailto:java400-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/java400-l>,<mailto:java400-l-request@midrange.com?subject=unsubscribe>

Sal,

I did notice one other difference between our two machines. I see from another
post that you have 500M of ram, I am running 1G. My old 170 ran WebSphere
like you describe and had 320M of ram. That was also V4R4. I do know that
500M is plenty for Tomcat.

David Morris

>>> sals@mrc-Productivity.com 09/12/01 01:01PM >>>
Sorry, I didn't add this earlier, I was out to lunch.  Our machine is at
V4R5 and has a CUM package likely from this Spring.  The machine is set to
adjust performance pools on the fly.  I guess I'm wondering if this is a
hardware issue or a WAS issue.  David's post leads me to believe that this
has more to do with WAS.  Maybe I need to try Tomcat on my AS/400 as well.
I just didn't want to go down that route if other people already have.

Sal

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.