performance question

[trupti nigam]

Hi All,

I was asked below question. Can someone please let me know what is the correct answer?
There is a firewall betwwn user interface and apache server and there is one more firewall between apache and the weblogic server.
The application is deployed (ear) in weblogic.There is no wls clustering. There is only onse server. If your application runs very slow and it's already in production, what is first thing , you will check?

Thanks,
Trupti

[Scott Johnson]

I would start with the application server and the database server. Verify the hardware is not a bottleneck (CPU/memory/IO bound).

Is something else running on the server that may be impacting your performance?

Use BEA's performance monitor to determine which kind of requests (which servlet(s)) are taking the longest. Drill down into the long running requests to determine exactly what code is slow.

Check the servlet thread pool and the db connection pool. Are they maxed?

I can't give you more specifics because I've never used Weblogic.

But if you check those areas, I think you'll see what causing the slowness and the solution will follow.

[Ravindra Rawat]

I would proceed as following on this.

1. Is the problem temporary? -> Check state/load on servers?
2. Check logs (assuming you log timings for interaction with other components) and find out time taken by individual components of the application or else profile your application. If weblogic is a problem then use techniques as suggested in pervious post.

Usually the culprits are database interactions, memory intensive loops or syncronization problems.

But check for basic things first and identify the components that are responding slowly and then analyse them.

Cheers
Ravindra

[Purushoth Thambu]

- For WebLogic Server you can check the throughput of WebLogic Threads (default execute thread) and the queue response time.
- Check the memory status.
- Take periodicall thread dumps.
- Finally the DB queries.

[Atish Ray]

Enable extended logs for Apache and check the elapsed time in apache access log first. First make sure it's the application does take lot of time and it's not the latency between user and your web servers. Then dig into your app infrastructure.

[Atish Ray]

Enable extended logs for Apache and check the elapsed time in apache access log first. First make sure it's the application does take lot of time and it's not the latency between user and your web servers. Then dig into your app infrastructure.