Re: webfacing problems...

Shane,

When this happens, do you see a lot of non-db page faults? If so, you
need more memory. Also, when memory gets moved between ASPs, it can
cause problems with Java's internal memory management. Your best bet for
maximum performance is to set up an ASP just for WebSphere that can't
have it's memory swapped out. IBM does have performance tuning guides
for WebSphere but you need to make sure you talk with the WebSphere
folks and not some other group.

Matt

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Shane_Cessna@xxxxxxx
Sent: Thursday, April 13, 2006 2:23 PM
To: WEB400@xxxxxxxxxxxx
Subject: [WEB400] webfacing problems...

Has anyone had any trouble with lag time in a webfaced application?
We're 
running WAS Express 5.0 and have some major issues.  Every few clicks 
(buttons or links), the webfacing job lags for around 5 to 10 solid 
minutes...this is becoming a major issue due to the fact that I'm doing 
some training with corporate executives and am taking a ton of heat over

this issue...

I've had multiple PMRs in with IBM for several months and nothing seems
to 
fix this issue...

Has anyone had the same problem?

Shane Cessna
iSeries Programmer
North American Lighting, Inc.
(618) 662-4483 x2776