AnsweredAssumed Answered

Wide ELAPSED_TIME variance on Auto-Suggest

Question asked by Dale_Stockman Champion on May 17, 2017
Latest reply on Jun 5, 2017 by Robert Ensinger

Looking at CMN_SESSION data due to user complaints about performance.  In the data, seeing large variation in ELAPSED_TIME when hitting  /niku/odata/GetSuggestionsForLookup

 

How large?  From less than 1 second to over 400 seconds.

 

The data doesn't indicate which auto-suggest field is performing slow for the user.

 

Can anyone manually suggest how we might identify the field (other than calling users - will do this if only way, but it's rather lame to call one's users to ask if they recall an auto-select field performing poorly, last week...

 

Or, does anyone know of any known conditions that might cause such variation (e.g. search lookup fields with dynamic queries using "X" code and remove "X" code...)?

 

Any other suggestions?

Outcomes