Richard, Before I went to API logs, I would start at Server Statistics. Sure you do not get as much granularity, but you should start tuning with the big knobs first anyway. :)
and more specifically I would look at the following first: 'Num Queue Items Blocked Count' 'Queue Items Blocked Count' 'ARServer Idle Time' 'ARServer CPU Proc-Time' 'Number of Threads' 'Network Responding Time' If your 'Num Queue Items Blocked Count' = 0 then you are likely not yet at your max configured threads. (Which can be compared with 'Number of Threads'.) 'ARServer Idle Time' should also give you some idea of how "busy" the server is too. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. Never ascribe to malice, that which can be explained by incompetence. On 8/1/06, Richard Baird <[EMAIL PROTECTED]> wrote:
Hi folks, Does anyone have basic rules of thumb for tuning the fast and list servers. I understand the proper way to approach it is to turn on API logging and look for waiting api calls, but are there any other guidelines to follow without getting the api log info. As an aside, how much of a perf hit does API logging impart on the server? Haven't used it on a busy prod server before. Thanks for any comments/suggestions. Richard
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
