PERFORMANCE [message #199121] Fri, 20 October 2006 05:32 Go to next message
Messages: 29
Registered: August 2006
Location: Bangalore
Junior Member

This is regarding performance.
In testing server,one status change which held in Frontend will
take 20 seconds and same status change in Production will take
2 minutes .
status change means Work in Progress to Finished and vice versa

Why this much difference in time to perform.

Sam chacko k
Re: PERFORMANCE [message #199125 is a reply to message #199121] Fri, 20 October 2006 05:56 Go to previous message
Messages: 3186
Registered: April 2005
Location: Heilbronn, Germany
Senior Member
Someome is running seti@home on Production? Wink

Possible reasons :

- Production server is somewhere at it's performance limit.
- Some one else was locking some of the stuff during the operation.
- The indexes and/or table statistics are different

To find out what is going on you will need to analyze what is going on.

How is the CPU / Memory load on the servers ?
Is one of the Servers swapping ?
etc, etc ....

To have a look at the statement level performance have a google for "sql trace tkprof", and pick one of the fine documentations there.
Previous Topic: About Mutating(Trigger)
Next Topic: performance issue on fetching values from an xml file stored into a CLOB column in DB (merged 2 thre
Goto Forum:

Current Time: Tue Oct 25 20:00:58 CDT 2016

Total time taken to generate the page: 0.14833 seconds