Thanks again ... I'll try this right away !
---------------------
Alain Menezes
ASLK-CGER Services GIE Tel.: +32 2 228.55.74
Rue Fossé-aux-Loups, 48 Fax.: +32 2 228.83.69
1000 Bruxelles Email:
a.menezes@aslk-cger.be
> -----Original Message-----
> From: James Shanks [SMTP:James_Shanks@TIVOLI.COM]
> Sent: jeudi 20 mai 1999 18:52
> To: NV-L@UCSBVM.UCSB.EDU
> Subject: Re: ovwdb - high CPU
>
> That's true but not recommended. You see, if your cache is
> significantly
> higher than the 5000 default, ovwdb will use more CPU and take longer
> to
> initialize. It allocates more cache when required, and then copies
> the all
> the old objects into the new cache before destroying the old one. And
> it
> may have to do this several times if you set the size to zero. Yes,
> it
> works but most folks don't like the overhead or the time penalty for
> complete initialization. So you save cycles by estimating the correct
> cache
> size for him. How many times has someone complained on this forum
> about
> his NetView being slow and then reported that raising the cache size
> fixed
> his problem? When your estimate is too low, it builds the cache in
> the
> same fashion as it does when you tell it to use zero.
>
> James Shanks
> Tivoli (NetView for UNIX) L3 Support
>
>
>
> "MENEZES, ALAIN" <a.menezes@ASLK-CGER.BE> on 05/20/99 12:39:08 PM
>
> Please respond to Discussion of IBM NetView and POLYCENTER Manager on
> NetView <NV-L@UCSBVM.UCSB.EDU>
>
> To: NV-L@UCSBVM.UCSB.EDU
> cc: (bcc: James Shanks/Tivoli Systems)
> Subject: Re: ovwdb - high CPU
>
>
>
>
>
> This works fine ...
> A little addition : when you configure a cache size 0, ovwdb can use
> as
> much as it needs for its cache !
>
> Thanks again
> ---------------------
> Alain Menezes
> ASLK-CGER Services GIE Tel.: +32 2 228.55.74
> Rue Foss << File: ATT04998.txt >>
|