Hi David,
The detailed log rows does not show that the API-call is taking much time.
There is a wait-time in between the calls, but...
If you look at the RPC ID, you see a jump from 0016990986 to 0016991463,
so the server has performed 477 API-calls between these calls. They may
have been thread executed by other threads.
Could arwklga have missinformed you?
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at http://rrr.se.
> Hi List
>
> I wonder whether anyone has come across a situation like this and can
> throw
> any light on what might be causing these performance issues.
>
> ARS Server 6.03.00 patch 013
> SunOS 5.10
> Oracle 9.2.0.5.0 64bit on remote machine (shared with other apps)
>
> Running arwklga against combined API+SQL logs throws up several lines like
> this:
>
> 2:40.5023 205245 actlink_set Wed Aug 29 2007 13:43:24.9652
> SELECT assignShort,assignLong FROM actlink_set WHERE actlinkId = 6881 AND
> actionIndex = 0 AND fieldId = 1077077
>
> 2:23.4299 191087 actlink_set Wed Aug 29 2007 13:32:39.6091
> SELECT assignShort,assignLong FROM actlink_set WHERE actlinkId = 6881 AND
> actionIndex = 0 AND fieldId = 1077077
>
> Looking at one of these in detail gives
>
> 205243 API 0016990986 List 390620 lp2d06 Wed Aug 29 2007
> 13:43:24.9636
> +EXECAL ARExecuteProcessForActiveLink from Remedy User (protocol 11) at IP
> address 152.78.134.145
>
> 205244 SQL 0016990986 List 390620 lp2d06 Wed Aug 29 2007
> 13:43:24.9638
> SELECT actlinkId from actlink where name = 'RPQ:SHR-Lock0'
>
> 205245 SQL 0016990986 List 390620 lp2d06 Wed Aug 29 2007
> 13:43:24.9652
> SELECT assignShort,assignLong FROM actlink_set WHERE actlinkId = 6881 AND
> actionIndex = 0 AND fieldId = 1077077
>
> 205246 API 0016990986 List 390620 lp2d06 Wed Aug 29 2007
> 13:43:24.9668
> -EXECAL OK
>
> 208592 API 0016991463 List 390620 lai Wed Aug 29 2007
> 13:46:05.4660
> +GLE ARGetListEntry -- schema RPQ:Log from Remedy User
>
> 208593 SQL 0016991463 List 390620 lai Wed Aug 29 2007
> 13:46:05.4675
> SELECT T201.C1,C8,C700037500,C700037000,C700034003,C700003000 FROM T201
> WHERE
>
> That is, these set fields actions seem to be taking a couple of minutes to
> complete. Looking at the objects involved, they are doing
> @@:Application-Generate-GUID or @@:Application-Confirm-Group processes.
> The
> +EXECAL to EXECAL OK is quick, but the thread then does nothing for 2
> mins
> 39 secs before the next action from another user.
>
> Is arwkloga misleading me when it says the actlink_set is taking 2 mins
> 40s
> is there an issue with the PROCESS actions? or is the thread just
> idle?
>
> Does anyone know what might take an Application-Generate-GUID process over
> 2
> minutes to complete? As far as I can see, list and fast threads usage are
> OK and the system is not waiting for a thread.
>
> Thanks for any advice
>
> David Sanders
> Remedy Solution Architect
> Enterprise Service Suite @ Work
> ==========================
> ARS List Award Winner 2005
> Best 3rd party Remedy Application
>
> See the ESS Concepts Guide
>
> tel +44 1494 468980
> mobile +44 7710 377761
> email [EMAIL PROTECTED]
>
> web http://www.westoverconsulting.co.uk
>
>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
> the Answers Are"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
