RE: [nv-l] High CPU Usage in ovwdb

["Barr, Scott" <Scott_Barr@csgsystems.com>]

I pound the crap out of nvcold. I have TONS of smartsets and they are all used in rulesets. The 8% isn't outrageous in my environment.

 

Tavve did come back with a patch recommendation. I will give that a shot.

 

My rulesets (and for those of you budding ruleset writers....)

 

1. Always block as first node

2. Always trap settings for second node.

3. THEN do the smartset query.

 

Stephen's comments about rulesets and nvcold are quite accurate. If you force OVWDB look ups more than necessary it will have a dramatic impact on performance. In my case, my environment is small enough and my machines are big enough to handle that.

 

Thanks Stephen, good reality check for me.

-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com]On Behalf Of Stephen Hochstetler
Sent: Monday, January 19, 2004 3:20 PM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] High CPU Usage in ovwdb

did the installation also create some new NetView smartsets? Are they complex ones? If you stop nvcold, do you quickly see ovwdb settle down?

this is just a wild guess, especially since I see nvcold at 8% cpu on your append.

years back when I was trying to do alot with nvcold I found some poorly written smartset rules cause a lot of lookups in ovwdb. you want the rule to reduce the objects looked through each time...otherwise nvcold will have ovwdb report the whole database..over and over and over which kills the cpu on ovwdb's part.

Stephen Hochstetler shochste@us.ibm.com
International Technical Support Organization at IBM
Office - 512-838-6198 (t/l 678) FAX - 512-838-6931
http://www.redbooks.ibm.com