Hi Brian
AFAIK, in both scenarios, all the work will be done by the escalation thread. The main difference is that in scenario 1 you have 4500 separate small transactions. In scenario 2 you have a single transaction modifying 4500 records. The potential problem with scenario 2 is that you may hit the filter limit on your server and stop the transaction. Regards David Sanders Remedy Solution Architect Enterprise Service Suite @ Work ========================== ARS List Award Winner 2005 Best 3rd party Remedy Application See the <http://www.westoverconsulting.co.uk/downloads/ESS_Concepts_Guide.pdf> ESS Concepts Guide tel +44 1494 468980 mobile +44 7710 377761 email [EMAIL PROTECTED] web http://www.westoverconsulting.co.uk <http://www.westoverconsulting.co.uk/> _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Brian Goralczyk Sent: Thursday, March 20, 2008 10:01 PM To: [email protected] Subject: Re: Efficiency question ** It is my understanding that the first process would happen quicker because the escalation is only running on one record. It does however require one aditional step. The reason for the display only field is so that the form will record an update and start the filters firing. It is running unqualified because I want it to fire on every record. So you are correct in that assumption. Am I wrong in my assumption that having the escalation run on one record that then fires a filter to every record in another form would cause the second action to become multi-threaded? The intention here is to cause the server to fire on as many LDAP records as possible as quickly as possible. The LDAP form is the slowest piece of the process. By FAR!! Brian Goralczyk On Thu, Mar 20, 2008 at 4:46 PM, Thomas Bean <[EMAIL PROTECTED]> wrote: ** Since both scenarios are triggered initially by an escalation, I'm thinking they are both running on the escalation thread. I could be wrong, but I don't think it matters that the second scenario is doing the push fields action to form A with a filter, as the initial trigger was an escalation on form C. If this is indeed the case, it would make sense to me that it takes longer for process 2 to complete, given the additional layers of workflow. One thing I'm curious about in process 2 -- what is the qualification for the push fields action in the filter that pushes the update to the display-only field on the ARDBC LDAP form? Is it running unqualified, pushing the update to every record in the form (which then triggers the filter that pushes to form A)? --Thomas ----- Original Message ----- From: Brian <mailto:[EMAIL PROTECTED]> Goralczyk Newsgroups: gmane.comp.crm.arsystem.general To: [email protected] Sent: Thursday, March 20, 2008 3:08 PM Subject: Re: Efficiency question ** Thomas, It is quite possible that having run over it so many times in my head I was not as thurough as I should have been. Let me clarrify. There are two possible processes. Process 1: Escalation on the ARDBC LDAP form pushes a copy of every record to form A, where all the work is performed on the data. This process causes the escalation to run on ~4500 records and takes ~7 minutes. Process 2: Escalation run on form C. This updates the one record, which causes a filter to fire that pushes an update to a display only field on the ARDBC LDAP form. This in turn causes each record to be pushed to form A, again where all the work is performed on the data. This process causes the escalation to run on one record and still process the same ~4500 records. This process takes ~12 minutes. It doesn't take a brain surgeon (which I am not) or a rocket scientist (which I am also not) to see that option one is the better way to go performance wise, however; this seems to go against what I have understood to be one of the advantages of using option 2. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
