|
Without working on your specific configuration issues,
it's difficult to narrow down the specific causes of
performance problems. Key things to look at:
1. Pre-compile JSPs (you've done that).
2. Pre-load frequently used WebFacing apps in WAS.
3. Minimize interactive jobs launched to one per user
(based on a user or group profile, bring them to a
single menu with their application options on it (you
can WebFace the menu too) to ensure only one interactive
job is created for each user session in WAS.
4. You may need to do some sort of load balancing by
creating other instances if WAS is having problems
with the number of sessions.
You can try profiling the application using a
profiling tool to figure out where the hot spots are
in WDSC Advanced version 5 (shipping after April
25).
It sounds like the problem is on the initial
activation of the interactive job and you need to look
at your system configuration to ensure that the system
is properly tuned to start any interactive job quickly
(how long does a regular signon take on green screen?).
Check the priority of the WebFacing interactive jobs
vs. other jobs on the system etc.
I've had good luck getting WebFacing to run well after
it's loaded and pre-loading the app may do the trick
if it's only slow for the first user signing on. ==================================
MORE INFORMATION ON THIS TOPIC
==================================
Ask your Web development questions--or help out your peers by answering them--in our live discussion forums.
The Best Web Links: tips, tutorials and more.
|
