[Fwd: Re: STATSPACK impact?]

   To get resonable results from the reports, your timing interval should be around 10 to 30 minutes.  As running statspack collection every that often is likely to produce far too much data than you want to have space for, I always recommend running statspack collection in a system like this repeatedly:
 Collect, wait 15 minutes, collect, wait long time, and then subsequently
do the reporting over the 15 minute intervals.

 And as to the impact:  There is in fact some impact on busy systems, which primarily comes from loading the statspack package into the library cache.
 The impact isn't large, and it is clearly worth doing.

 Thanks, Bjørn.

 Joe Raube wrote:

  I have run it as frequently as once per hour, often times just 2 or 3 times per day - morning, noon, close of business.I have never seen any performance impact, and I don't believe therewill be any unless you change the default level of statistics gathering.-JoeOn Wed, 06 Feb 2002 12:47:48 -0800Thomas Jeff <ThomasJe_at_tce.com> wrote:   

    Just curious, but if your shop uses STATSPACK, could you tell me howfrequently you run it, particularly in your OLTP databases; and whether you've noticed anyperformance issues with generating frequent STATSPACK snapshots?Thanks.--------------------------------------------Jeffery D ThomasDBAThomson Information ServicesThomson multimedia Inc.Email: thomasje@tce.comDBA Quickplace: http://gkmqp.tce.com/tis_dba-------------------------------------------- 
    
    _________________________________________________________Do You Yahoo!?Get your free @yahoo.com address at http://mail.yahoo.com