Here's a snippet of what's happening - User ID's and IP addresses removed (XXXXXX, 1.1.1.1 are not real obviously):
/* Wed Aug 13 2008 12:50:07.6113 */+GMCRS ARGetMultipleCurrencyRatioSets -- as user XXXXXX from Mid-tier (protocol 13) at IP address 1.1.1.1 /* Wed Aug 13 2008 12:50:07.6517 */+GMCRS ARGetMultipleCurrencyRatioSets -- as user XXXXXX from Mid-tier (protocol 13) at IP address 1.1.1.1 /* Wed Aug 13 2008 12:50:07.6983 */+GMCRS ARGetMultipleCurrencyRatioSets -- as user XXXXXX from Mid-tier (protocol 13) at IP address 1.1.1.1 /* Wed Aug 13 2008 12:50:16.0895 */+GMCRS ARGetMultipleCurrencyRatioSets -- as user XXXXXX from Mid-tier (protocol 13) at IP address 1.1.1.1 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Wednesday, August 13, 2008 8:12 PM To: arslist@ARSLIST.ORG Subject: Re: ARGetMultipleCurrencySetRatios X a zillion Can you post an entry from the api logs for one of the calls? Axton Grams On Wed, Aug 13, 2008 at 3:31 PM, William Rentfrow <[EMAIL PROTECTED]> wrote: > ** > I have been troubleshooting an unrelated problem. In 40 minutes of > server side logging I have 509 instances of this API call happening. > Each one is about 4/1000 of a second long or a total of 2 seconds of > time in 40 minutes = 3 seconds of time an hour. > > Granted this is very small - but I am in a large environment and we > are having performance problems. Every one that can be solved will > be. However, I am not too familiar with what controls this API call. > Since we are doing zero financials and no foreign currency this call > is not (strictly speaking) needed. > > The server configuration guide (7.1) says the "Currency Ratio Cache > Refresh Interval" is the setting to change for this. It's defaulted > to 60 seconds meaning each client will check the ratios once every > minute. This makes complete sense to me if you are dealing in any > financials with foreign currency. > > However, I can see in the logs that this API call happens a LOT more > than every 60 seconds- like every few seconds during a save of an > Incident for example. It's called 4 times in 13 seconds for the same > user (and 3 of those are in the span of 1/10 of a second) in one > example and this just seems pointless. > > Anyone know how to slow this down to something more like once an hour > per user? It's overkill X a zillion right now. > > William Rentfrow, Principal Consultant [EMAIL PROTECTED] C > 701-306-6157 O 952-432-0227 > > __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" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"