nv-l
[Top] [All Lists]

RE: [nv-l] Stress Testing NV, looking for opinions

To: <nv-l@lists.us.ibm.com>
Subject: RE: [nv-l] Stress Testing NV, looking for opinions
From: "Van Order, Drew \(US - Hermitage\)" <dvanorder@deloitte.com>
Date: Thu, 3 Jun 2004 11:35:58 -0500
Delivery-date: Thu, 03 Jun 2004 17:47:52 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
Importance: normal
Reply-to: nv-l@lists.us.ibm.com
Sender: owner-nv-l@lists.us.ibm.com
Thread-index: AcRJgkIKp/dmArsmSJaASO+DjVPEZwAAdcYQAABXbXA=
Thread-topic: [nv-l] Stress Testing NV, looking for opinions
I got the base script from IBM support and have no problem sharing if someone from IBM weighs in with no objections. We are running these traps through TEC_ITS.rls, so nvcorrd, etc. should be getting exercised. I would like to put a mix of traps in as well, but am not a developer so I'm making do right now.
 
Funny you mention Query Smartset node; we are pretty sure this was the major source of our trouble. Ours happened to be there for no good reason, so we removed it and cycled the daemons. In addition, we did minor things like configure trapd to save logs for a week, and implemented a weekly ovmapcount/ovtopofix process. NV has been smooth ever since. Until then, NV had been hanging at least once/week, and we were thinking NV was choking on the number of traps, which we now believe to be bunk based on testing. MLM was considered to be the solution until we learned our addressing scheme was not compatible. That's when we opened a support call--been at this for about a month now.
 
We're also ready to up the number of traps to see where NV falls over. When this started, we got information from support that NV could handle sustained 6-8 traps/second. I've got the email somewhere...  It appears that number is conservative.
-----Original Message-----
From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of Barr, Scott
Sent: Thursday, June 03, 2004 11:03 AM
To: nv-l@lists.us.ibm.com
Subject: RE: [nv-l] Stress Testing NV, looking for opinions

One other thing - the use of smartsets and rulesets heavily affects performance. It would be beneficial if your testing included a variety of traps, not the same one over and over. In addition, pushing them through rulesets if possible would be a real good stress test especially if you have rulesets doing a "query smartset" node.
 
Would you be willing to share your script that generates the traps? I am interested in doing the same thing.


From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of Brett Coley
Sent: Thursday, June 03, 2004 10:44 AM
To: nv-l@lists.us.ibm.com
Subject: Re: [nv-l] Stress Testing NV, looking for opinions

That sounds like a valid way to test, but I'm thinking
you may want to throw in some more randomness, maybe
some heavier peaks.   Sounds like the 250 in 50 secs are
dealt with ok in their 10 minute window, but what happens
with a burst of 1000 thrown into the mix?
 
Regards,
Brett
Tivoli Software/IBM
 
 


This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web