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



Ricky,

You're probably memory constrained for starters. 1 gig is not much
memory for a Java app (or a busy site running CGI for that matter) and
if you have other stuff happening on this box, there just isn't any way
you have enough memory. If you look at the Non-DB Pages on WRKSYSSTS
(let it run for a few minutes), you'll probably see a very high paging
rate in at least one of the pools. Someone (either here or on
Ignite/400's list) posted an IBM whitepaper that talked about paging
rates and they recommend under 100 for best performance. Our 720 is just
a staging box for our web apps and I know it doesn't take much to push
it well past that (for example, starting WAS Express will push it up to
700 for about 5 minutes -- nothing happens while that's going on).

Besides the JSP compiles the first time you hit a web app, OS/400 also
does some one time stuff to all of the Java classes (this also happens
to JSP pages after they are compiled) that makes them run faster when
it's done. Unless you're really memory constrained, you should see
performance improve as you use the application.

One other thing I didn't think of before: If the admin GUI you're using
is the one for WebSphere, it's just plain slow. The best advice I can
offer on it is to enable and start the adminconsole application and use
it instead. It's much faster than the one that's part of the HTTP
Server's admin GUI.

Matt

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Ricky Thompson
Sent: Thursday, August 11, 2005 1:48 PM
To: web400@xxxxxxxxxxxx
Subject: RE: [WEB400] Slow Web Admin

Thanks guys..  I was just playing around with webfacing a few programs
and
it's taken me about 3 hours to do one very small program.  I finally got
the
application installed and now I'm running it for the first time off the
AS/400.  It takes it almost 10 mins to load the Web Faced App.  Does
anyone
actually use webfacing for a viable option.  Do you have to have 12-way
processor to get suitable results.  Boy I guess I better go buy Brad
Stone's
book.  Long live CGIDEV2 :)

Thanks again guys. 

date: Thu, 11 Aug 2005 12:22:59 -0400
from: "Haas, Matt" <Matt.Haas@xxxxxxxxxxx>
subject: RE: [WEB400] Slow Web Admin

Ricky,

We also have a 720 with 1 gig of memory and it's dog slow (especially
the first time you use it). Installing JDK 1.4 with the latest group
PTF's will help some but chances are you're either paging like crazy or
you have enough going on that it's CPU bound (you'll need to do some
investigation to see where your problems are). The 8xx and newer
hardware runs Java much better (the admin GUI for the Apache servers are
Java based) so short of buying a new box, your best bet for managing the
HTTP servers is probably going to be from the command line. About the
only things you can't do from the command line are create new HTTP
servers (not entirely true but it's not documented and there's a lot of
configuration you need to do manually) and manage certificates.

Matt



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.