E9.2 How do you analyse poor performance in Web?

MacaqueJDE

Active Member
Hi there!

I was wondering how you guys proceded when all of sudden your JDE web Application slowed down. Like for my case, from time to time, my users will call me because just switching from menu to menu will take 5-6 seconds vs usually instant.

The issue resolve itself after like 20 mins, but I still find myself wondering how I can detect where the issue comes from.

What I usually do :

Check for any in process UBE.
Check my MSSQL database for any lock / block / long request.
Check for zombies.
Check Entreprise Server process load.

But Still I don't see anything out of the ordinary.

Do you guys have any tricks?

Thanks!!
 
Do you have any backup software clients on your servers? We had a BackupExec client on our db server that would cause 30 second freeze-ups once every few hours. Eventually we found it and disabled it during our normal production hours.
 
When you have a slow down in the web, I first check if it is pervasive at that site, I run 6 weblogic instances so if it is pervasive at the site, then I figure it is WAN/LAN related. If it isn't pervasive, I next check if the weblogic instance they are attached to has an issue. I can normally tell because the Java process for that instance is using an inordinate amount of CPU compared to the other instances on the box.

If neither of these are true, then I start checking kernels to see if one of them is misbehaving. First I check for high CPU, next I'll start looking at logs for issues, errors, locks, etc.

This is rather high level, but hopefully it will help get you started.

Tom
 
Do you have any backup software clients on your servers? We had a BackupExec client on our db server that would cause 30 second freeze-ups once every few hours. Eventually we found it and disabled it during our normal production hours.

Ahaha I feel you, server backup have caused a lot of issue in the past for us too. Also leaving a VM snapshot on the servers also slowed down everything, not sure why.

When you have a slow down in the web, I first check if it is pervasive at that site, I run 6 weblogic instances so if it is pervasive at the site, then I figure it is WAN/LAN related. If it isn't pervasive, I next check if the weblogic instance they are attached to has an issue. I can normally tell because the Java process for that instance is using an inordinate amount of CPU compared to the other instances on the box.

If neither of these are true, then I start checking kernels to see if one of them is misbehaving. First I check for high CPU, next I'll start looking at logs for issues, errors, locks, etc.

This is rather high level, but hopefully it will help get you started.

Tom

Thanks that's great. I hoped there was some kind of diagnostic tool. Still you gave me some idea, that will help me next time. :)
 
Back
Top