Hi List, I'm sorry if this has been covered before; but you can tune some of the impact that the recon jobs have on the AR server by restricting/reducing the number of threads it can use.
By configuring an RPC for your recon engine and setting a moderate number of threads to this RPC; you could "throttle-down" how much processing grunt is available to recon jobs. This may slow down reconciliation, but will reduce impact to the rest of the system. Obviously, there is a limit to how much work one AR server can do, so in the end, you may still need to setup a Server group. It will take some testing to find the right balance of threads for your AR server and reconciliation load, but trying this will be easier/faster than implementing a new server. You might also want to double-check that the identification fields being used for the merge operation are properly indexed. They may be inefficient. On the subject of BMC's recommendation around Server Groups and dedicated "non-user" AR servers, page 12 of the 'Reference Architecture for BMC Service Support Solutions" whitepaper provides some brief guidance on this topic (very brief, but it's there): ....Using servers dedicated to specific functions provides an excellent way to scale the installation. The medium and large configurations described in this document use a dedicated integration server. This server is not part of the load balanced environment, and so does not see any end user activity. However, it is part of the AR System server group and so uses the same database. To relieve the load on other servers in the group, assign all batch and integration operations such as reconciliation, Atrium Integration Engine (AIE), and escalations to this server. Anyway, hope this helps. Note - this is my first ARSList post, so go easy please. :) Allan O'Farrell The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of patrick zandi Sent: Tuesday, 22 September 2009 4:39 AM To: [email protected] Subject: Re: Reconciliation process time and power ** makes sense, but I thought Price was more or different.. plus you need more servers physically.. Thanks On Mon, Sep 21, 2009 at 1:23 PM, Guillaume Rheault <[email protected]<mailto:[email protected]>> wrote: ** That is right, the recommendation is to have a server group in which you have a dedicated server for "admin tasks"that will run the tasks that I listed below. Where is this written? Well it is not written anywhere publicly. However, I have personally talked to BMC Remedy consultants and architects from BMC Global Services (the consulting arm of BMC) and that's what they recommend. I guess eventually this knowledge will be formalized as a best practice architecture. We have that architecture set up in production, and works very well, so going forward, that's what is recommended for ITSM customers that have a CMDB implementation that involves reconciliation. The minimum for the server group is 2, one server dedicated to "admin/recon tasks", and the other one user facing. So if you have three servers, one for admin/recon tasks, the other two servicing users. Make sure you configure your load balancer so no user request gets forwarded to the "admin" server. -Guillaume -----Original Message----- From: Action Request System discussion list(ARSList) on behalf of patrick zandi Sent: Mon 09/21/09 12:46 PM To: [email protected]<mailto:[email protected]> Subject: Re: Reconciliation process time and power Are you saying the Recommendation is using a Server Group? I don't see any need for that, unless you might be talking 15K nodes... and a over million relationships.. I would think. how many in the minimum for a server group??? what are they saying about that... Where is this written? On Mon, Sep 21, 2009 at 12:35 PM, Guillaume Rheault <[email protected]<mailto:[email protected]>>wrote: > ** > > It is now a common admission/recommendation that a dedicated server should > be used in production for the following, to run the following: > > - escalations > - reconciliation jobs > - approval server > - assignment engine > - email > - SLM > > This means an extra server license unfortunately. > > -Guillaume > > > -----Original Message----- > From: Action Request System discussion list(ARSList) on behalf of patrick > zandi > Sent: Mon 08/17/09 2:37 PM > To: [email protected]<mailto:[email protected]> > Subject: qq: Reconciliation process time and power > > Quick Question: > ARS 7.1 > CMDB 2.1 Patch 6 > Solaris 10 > FD, and CM. > > --- > When running oob jobs it uses 97% of 16 CPU's making the aruser tool and > mid-tier Sluggish at best for over 1 hour. > > What are others seeing? > > -- > Patrick Zandi > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at > www.arslist.org<http://www.arslist.org/> > Platinum > Sponsor:[email protected]<mailto:sponsor%[email protected]><sponsor%[email protected]<mailto:sponsor%[email protected]>>ARSlist: > "Where the Answers Are" > > _Platinum Sponsor: > [email protected]<mailto:[email protected]> ARSlist: "Where the > Answers > Are"_ > -- Patrick Zandi _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org<http://www.arslist.org/> Platinum Sponsor:[email protected]<mailto:sponsor%[email protected]> ARSlist: "Where the Answers Are" _Platinum Sponsor: [email protected]<mailto:[email protected]> ARSlist: "Where the Answers Are"_ -- Patrick Zandi _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
