Author |
Message
|
kriersd |
Posted: Tue Apr 22, 2003 10:19 am Post subject: Websphere tuning for high volume |
|
|
 Master
Joined: 22 Jul 2002 Posts: 209 Location: IA, USA
|
Does anyone have any tips or tricks used to tune the Workflow web client running under Websphere. We have a large scale Workflow application that seems at times to show slow response using the web client. _________________ Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
Back to top |
|
 |
jmac |
Posted: Tue Apr 22, 2003 10:44 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
Dave:
One thing you should do is make sure you are not writting the Log. It is way too verbose. Its too bad that there isn't a way to have it only log errors. _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
kriersd |
Posted: Tue Apr 22, 2003 12:41 pm Post subject: |
|
|
 Master
Joined: 22 Jul 2002 Posts: 209 Location: IA, USA
|
Do you mean the servlet-out.log and servlet-err.log? _________________ Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
Back to top |
|
 |
kriersd |
Posted: Tue Apr 22, 2003 12:51 pm Post subject: |
|
|
 Master
Joined: 22 Jul 2002 Posts: 209 Location: IA, USA
|
The servlet-out.log is already 11mb and we clear the logs nightly. Could this be our problem? _________________ Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
Back to top |
|
 |
jmac |
Posted: Tue Apr 22, 2003 12:51 pm Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
Dave:
I am talking about the HTML Client log that is specified via the Logfile parameter in WebClient.properties. For instance:
Code: |
Logfile=d:/mqworkflow/cfgs/FMC1/log/servlet.log |
Just take a look at the amount of information put in by a logon, or a jsp that has a large number of parameters defined. This file can get pretty big quick on a heavily used system, and thus I am sure could be a potential bottleneck _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
kriersd |
Posted: Tue Apr 22, 2003 5:44 pm Post subject: |
|
|
 Master
Joined: 22 Jul 2002 Posts: 209 Location: IA, USA
|
Yeah, I didn't think that was the issue.
We did not enable the log file in the Webclient.properties file.
Dave _________________ Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
Back to top |
|
 |
slnelson76 |
Posted: Wed May 07, 2003 12:36 pm Post subject: Tuning |
|
|
Novice
Joined: 02 Apr 2003 Posts: 13 Location: Iowa
|
First you get IBM to admit.....ERM nevermind.
This isn't really a post in response to kriersd, but rather a further explanation of the problem.
The performance problems that he is talking about involve using an out of the box plane jane server. WebSphere 3.5/WF 3.3.2.4
Under heavy load we see a very linear scaling factor. After about 6 concurrent hits to the web server we see terrible performance. Yet the CPU is running about 5-10%. This lead us to believe that their is some sort of synchronization constraint inside the code.
We have tuned just about everything we can think of. Any ideas as to what might cause this? |
|
Back to top |
|
 |
slnelson76 |
Posted: Tue May 27, 2003 12:01 pm Post subject: SOLVED....Sorta |
|
|
Novice
Joined: 02 Apr 2003 Posts: 13 Location: Iowa
|
For those of you who might be wondering at our performance issues.....Here's the cause....
Windows + Web Client + SMP = BAD PERFORMANCE.
Windows + Web Client + SingleCPU = GOOD PERFORMANCE
Wierd huh......
Try it if you can.
Websphere 3.5 with IBM jdk 1.2.2
or Tomcat with Sun jdk 1.4.(whatever)
WF Webclient 3.3.2 or 3.3.0
Load-test tool of your choice.
Hammer the box with multiple CPU's responding.....Bad Performance
Hammer the box with Processor Affinity of the process set to 1 processor....good performance.
BTW IBM Labs in Germany told us about this one.
-Steve |
|
Back to top |
|
 |
|