	Product(s):	APM Implementation and Performance Management
	Version(s):	6.2+
	Environment:	N\A
	Area:	N/A
	Subarea:	N\A

How to use APM logging to debug performance issues when displaying views and/or dialogs.

Background

If logging in to a Site view performs poorly, or moving around Site views peforms poorly, try logging database access for poorly performing queries. This is primarily an issue with MCLB configurations that may require an index to improve performance.

Steps to Accomplish

Open the Settings Editor for the server instance(s) that runs the smart-client service, and add the following logging:

Open the Settings Editor for the Service that runs the smart-client server instance(s).
Click on the Logging tab.
On the What to Log tab, click on the New Rule toolbar button ( ), and select the New Empty Rule option.
On the New Rule dialog, enter Ivara.Pers.Slice.Performance in the name property, and set minlevel to Warning.
Click the OK button to save.
Select the File -> Show Advanced Settings option.
On the Settings tab, select the Diagnostics node in the lefthand pane. In the righthand pane, under Performance Profiling, change the threshhold value from 1000 millisends (i.e., 1 second) to a larger value closer to the performance timng that you are seeing (e.g., 10000 milliseconds, or 10 seconds).
Click the Save button on the Settings Editor dialog.
Start the Service that runs the smart-client server instance.

After logging in and/or navigating to problem views, review the service's server log file, searching for messages that pertain to the Ivara.Pers.Slice.Performance category, such as the folllowing:

Ivara.Pers.Slice.Performance [10] File: oqtempl.h(2383) : Poor performance was detected for a slice. Fetchnext() took 1219ms to execute which exceededs 1000ms (Profile Slice Threshold setting). The slice query is:

SELECT u.Lang,u.Text,u.UIText_oi FROM OQ.UITextLanguage u WHERE (upper(u.Lang)='EN-CA' OR upper(u.Lang)='EN') ORDER BY u.UIText_oi ASC

If you require assistance with the log file review, please submit at Service Request to APM Support clearly stating the problem area. Be sure to attach the smart-client server logs, including user action logs, to the Service Request.

NOTE: After messages have been logged for the performance problem areas, remember to turn off the slice performance logging. This can be accomplished by returning to the Settings Editor utility, and deleting the Ivara.Pers.Slice.Performance logging rule. The change will be effective immediately, so there is no need to stop & restart the smart-client server instance.

The problematic queries should be provided to your Database Administration team to analyze and test adding targeted index to improve performance.

Indexes can sometimes improve performance in one area, at the expense of performance in another. Performance testing should be done based on your common Use Cases.

When an Index is a keeper, refer to our Help on how to make it a permanent addition to your APM Index register to that it will be maintained through upgrades going forward.

Investigating Performance of Site Views

See Also