Skip to Content
Information
This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Identifying Distributed Server Option performance issues

Perform the following steps to investigate performance issues in processing Distributed Server Option (DSO) operations:

  1. Determine the number of entries in DSO Pending Operation:
    1. From AR System Administration Console, select System > Distributed Server Option > Pending DSO Operations.
    2. Search for operations with CreateDate before $DATE$.
    3. After a minute, refresh the search to determine how many operations were processed in a minute.
    4. Determine the rate at which they are processed.
  2. Perform the same process against each pool, to see if each is processing pending operations.
  3. Determine if the rate of operations is in proportion with the requirement. If the rate is satisfactory, but there are many operations to process, there may be a large data load to process and no further investigation may be required.
  4. Verify that the value of DSO pools are set based on the requirement. Increasing the number of DSO pools increases the processing load on the server, but provides more parallelism. Verify that you have sufficient ARServer threads defined to accommodate the pools.
  5. If required, set a polling interval for the DSO server.
  6. Assign DSO to a specific RPC ID.
  7. Investigate performance issues, if necessary.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

AR System 21.3