|
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 -----Original Message----- From: java400-l-admin@midrange.com [mailto:java400-l-admin@midrange.com]On Behalf Of Blair Wyman Sent: Wednesday, September 12, 2001 1:51 PM To: java400-l@midrange.com Subject: RE: Servlet Load Times under WAS on an iSeries! I must admit that the hardware aspect didn't occur to me at first, though the long startup time -- relative to total run time -- seems somewhat incongruous. It might be worth watching WRKSYSSTS to see if the storage pools appear fairly balanced as the servlet runs. (Thrashing is a potential problem on any '400 if the pools aren't properly balanced.) Also, knowing the Version/Release/Modlevel of the operating system could still be helpful. -blair Blair Wyman -- iSeries JVM -- (507) 253-2891 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "I was born not knowing, and have had only a little time to change that here and there." -- Richard P. Feynman "Joe Pluta" <joepluta@PlutaBro To: <java400-l@midrange.com> thers.com> cc: Sent by: Subject: RE: Servlet Load Times under WAS on an iSeries! java400-l-admin@mi drange.com 09/12/2001 11:19 AM Please respond to java400-l I talked to Sal about this offline, just to make sure I understood, and we came to the conclusion that it's probably his machine. Sal's running a 270-2248, and we've both heard whispers that it doesn't have an L2 cache, unlike my 270-2250. Also the 2248 has a CPW of 150, and the 2250 has a CPW of 370, and my machine has twice the memory of Sal's. All these together make my machine run maybe 10 times faster on an initial servlet load. There's little or nothing that can be done about that, short of preloading the servlets. I think we'd all appreciate hearing from anybody else about this, especially the L2 cache issue. Joe > -----Original Message----- > From: Sal Stangarone Jr. > Sent: Wednesday, September 12, 2001 10:02 AM > Subject: Servlet Load Times under WAS on an iSeries! > > I have some simple servlets that I've deployed on our iSeries > under both WAS > 2.02 and 3.5.2 and in both instances the initial load times are > unacceptable > (15 seconds or more). Once loaded they perform well (under 2 seconds). I > know I can have the Servlets loaded as part of the WAS startup but I don't > understand why these servlets take so long to load on our iSeries. I've > deployed the same servlets to a standalone PC utilizing Tomcat as > the server > and I see minimal (under 5 seconds) startup time needed there even though > its a small PII 233 PC. > > I have tried optimizing my class file to opt 40 and while that has some > effect it's minimal. Has anyone else experienced this? Is this WAS or my > iSeries any ideas? _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l. _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l or email: JAVA400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l.
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.