7000 an hour is only 2 a second so I’d suggest there’s something wrong somewhere – I guess you’ve turned logging on?
I’d expect around 10 a second for a system that hasn’t been tuned but this is just for merging, not for the initial identification. Is this a one-off load after which only deltas will be loaded? If you’ve got a million CI’s to reconcile every night then you’ll struggle unless you get the sort of architecture that BMC used for performance testing. Is there any custom workflow that could be disabled? Can you disable any normalisation? If the CI’s are being identified then this could be what is causing the poor performance. If so, do the CI’s need to be identified or can you just create the reconid’s as the CI’s are initially created? From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rick Cook Sent: 23 June 2014 17:48 To: [email protected] Subject: Re: Reconciliation speed ** Drop the indexes on the destination forms? Rick On Jun 23, 2014 9:47 AM, "William Rentfrow" <[email protected] <mailto:[email protected]> > wrote: ** Hi - We're trying to get our recon jobs faster. We have hundreds of thousands of CI's in certain classes and we will have over a million in some other classes. Right now we're getting about 7000 per hour - which means the tool are basically unusable because it takes waaaaaaaaaaaaaaaaaaay too long to go through a recon job. This is with dedicated servers and having gone through many (all?) of BMC's performance tuning papers we're still not able to get much faster than that. William Rentfrow [email protected] <mailto:[email protected]> Office: 715-204-3061 <tel:715-204-3061> Cell: 715-398-5056 <tel:715-398-5056> _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
