This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

To view the latest version, select the version from the Product version menu.

Assessing relevance of performance issues

To maximize the performance improvement for a particular operation, the goal is to:

  • Improve the performance of API calls or threads.
  • Focus on operations that occur frequently.
  • Focus on operations that are relevant to the user or activity encountering the performance issue.

An API operation that is slow and occurs frequently can have a larger performance impact than an infrequently used API call that is displayed in the Top N longest-running individual API calls. This topic provides guidance for evaluating the relevance of slow API calls on the reported performance issue.

Before you begin

Before you begin, ensure that you have performed the following tasks to identify performance issues:

To identify relevant API calls for further investigation

  1. Under API Aggregates, click by User.
  2. Scroll through the list. looking for the largest values of AVG TIME for the user encountering the issue.
    If the combination of API, Form, and User occurs more than 100 times, and the Avg Time is greater than 3 seconds, improving the performance is generally relevant to the user.

To determine whether slow API calls are related to the reported performance issue

  1. Under API Aggregates, click Top N and view API calls with Start Time consistent with the issue that the user reported.
  2. Click the line number to view the log entry.
  3. Check whether the user column indicates the user reporting the issue.
  4. Repeat the procedure for each of the API calls listed in the Top N with Start Time consistent with the issue that the user reported.


    End users most frequently report issues related to ARCreate or ARSetEntry API calls. These API calls occur for creating or modifying entries, and should be easy to diagnose.

  5. Under API Aggregates, click Exceptions.
  6. Click the line number to view the log entry.
  7. Verify whether the User column indicates the user reporting the issue.
  8. Under API Aggregates, click Exceptions to return to the list of API exceptions.
  9. Repeat steps 6 – 8 for each API exception.


An administrator identifies a long-running API call by investigating the Top N API calls.

The API call is a GLEWF on BMC.CORE:BMC_Impact_D, which can take more than 18 seconds to complete.

Under API Aggregates, the administrator clicks By Form.

The following results are displayed:

(Click the images to expand it.)

Reviewing the counts of API calls shows that the one that can take a long time was issued 816 times, which was a significant number during the test. The AVG TIME to complete the API call was a reasonable 0.1567 seconds, but the instances when it did take a long time pushed the SUM TIME to be over 2 minutes, compared to 11 seconds to process a similar number of API calls on BMC.CORE:BMC_Dependency.

The administrator concludes this slow API call is relevant to the overall performance issue captured in the logs.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.