What is the best strategy to evaluate performance of a big system
- From: Eriovaldo Andrietta <ecandrietta@xxxxxxxxx>
- To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Sat, 24 Sep 2011 12:46:57 -0300
Hello Friends,
I would like to know, what is the best strategy to identify and provide
performance in a big system that is running in the production.
Imagine a system written in java, C, perl, pl/sql, triggers ... and others
... several kinds of language ..
Everything is connecting to Oracle 10g, doing small queries and complex
queries too ...
So ...
I understand that there must have "pointed bad queries" that can be
identified only running the applicaton ... It maybe take more time than the
expected...
What would be the other way to obtain the problematic queries?
- Turn on trace, read the tracefile, identify problems and make changes
based on trace ?
- Analyse application logs, read the log, identify problems and make
changes based on log ?
- The tester identify problems by himself, testing all
system functionality ? In this case, trace and log are resources to obtain
the bad sql statment.
What is the best option for environment ?
- Apply the strategy on the production environment, without leaving this
database to another environment, because this
action will reorganize the database and provide a different data
organization in comparison with the original environment and probably
different performance.
- Apply the strategy on new database (using same database parameters) in
another environment and populate it with the data from the production
environment and use trace or logs ?
At first, the resource for it would be : a tester skill and a DBA skill
professionals.
Thanks and Regards !!
Eriovaldo
--
//www.freelists.org/webpage/oracle-l
Other related posts:
