Re: timed_statistics anyone?

According to "Tuning Oracle" by Oracle Press (ISBN 0-07-881181-3), setting TIMED_STATISTICS to True will result in a 11 percent Performance hit.

This parameter was not intended to be left on. It is used in conjuction with the UTLBSTAT/UTLESTAT to monitor database performance.

You first set Timed_statistics to true, then run Utlbstat, then after a period of time, run Utlestat, then change Timed_statistics to False.

Hope this info helps...
Satar Naghshineh
In article <36307338.261511663_at_news.demon.co.uk>,   marc_at_otbbb.demon.co.uk (marc bowden) wrote:
> Hi All
>
> I would like to get an idea of the affect on performance of switching
> this on. Specifically, I what I want to know, is what is the change
> in system behaviour when ts wre switched on.
>
> If, eg, statis. are monitored once a second, with little usage of cpu
> or memory and some small amount of data is updated, then it would seem
> feasible to leave them on all them time on a production database.
>
> On the other hand, if sampling is every few milliseconds and tens of
> thousands of rows are written to some system table somewhere then I'd
> take turning them on as an occasional luxury! :-)
>
> The answer presumably lies somewhere in between these extremes - can
> anyone enlighten me please?
>
> A Bientot
> Marc
>
>

--
Oracle DBA/UNIX System Admin
Advanced Enterprise Solutions
(949) 756-0588
Oracle Re-Seller

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Thu Oct 22 1998 - 16:23:41 CDT