Remedy - Performance and Tuning Required Settings for 9.0 and 9.1

Version 5

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    Remedy AR System Server


    AR System Server


    BMC Remedy AR System Server 9.0 and 9.1


    What are the Best Practice settings for  Performance in AR System v9.0 and 9.1?



    Note: This article covers  the recommended steps for performance and stability .  Please review the complete list of recommendations in the master article,  ‘Remedy 9.1 Upgrade Recommendations’, before proceeding.

    The following list of performance tuning steps are required for all 9.0 and 9.1 environments. This list has been created based on existing 9.x production environments in collaboration across BMC and multiple customers.   

    1. Run the config checker.
    This will help to identify and and address anything flagged.
    See the on-line documentation for more information about the checks and remediation steps.

    2. Check the Database Parameters required:
    For Oracle:
              - Make sure the stats are up to date
              - Set Cursor Sharing in the database to EXACT
                From 9.x onwards, Remedy uses bind variables, so cursor_sharing needs to be set to default value “EXACT” in the database.

                Oracle cursor sharing has been documented in the following documentation below:

              - Set "_b_tree_bitmap_plans" to FALSE in the database.  
                 Oracle parameters and sizing recommendations are documented in the performance tuning guide:
    For MS-SQL:
              - Make sure the stats are up to date
              - Set the READ_COMMITTED_SNAPSHOT to ON
              - Set the PARAMETERIZATION to SIMPLE

                MS-SQL Parameters have been documented in the following documentation below:

    3.  Apply the most current patch and hotfix package for the AR Server and Mid-tier
    Please check the available Hot Fix bundles in the following FTP location:
    Note: In the case of having a Server Group, the Hot Fix(es) need to be applied on all servers in the Server Group.

    4.  Set the Java 
    Heap Size for AR Server:
    Due to the changes in AR System version 9.x, setting heap size properly is required to ensure memory is correctly allocated.   

    Note:  9.1 SP2 Installer will automatically set the Java settings in arserver.config to Best Practice settings.
    After installing or upgrading SP2, check these settings in case they need to be adjusted for your environment.
    Lower 9.x versions will need to follow the settings mentioned here below.

    Set jvm.maximum.heap.size.
    This needs to be set in arserver.config (Windows only) located in the ‘ARSystem’ directory.
    For Linux or Solaris, the file name is arserverd.conf.

              - Medium size environments with 800-2,000 concurrent users and 16 GB RAM,

                                   set jvm.minimum.heap.size to at least 8589934592 .
                                      set jvm.maximum.heap.size to at least 8589934592.
              - For a Large environment (2000-5000 concurrent users and 32 GB RAM)

                                      set jvm.minimum.heap.size to at least 21474836480.
                                      set jvm.maximum.heap.size to at least 21474836480.

                Add additional garbage collection parameters (for jdk/jre 1.8):  

    Note: For jdk/jre up to 1.7, use PermSize in place of MetaspaceSize, i.e., use -XX:MaxPermSize=512m -XX:PermSize=384m
    Check the 
    article:   000113248   to know the required steps to set these values.

    Set jvm.minimum.heap.size to the same value as jvm.maximum.heap.size

    See the following link for mo  re details on this requirement:

    5.  (Linux Only) Set the NPROCS value appropriately:
    The System admin need to monitor the thread usage (nproc value) during the peak periods and adjust the value accordingly. Please take the help from your system admin to correct/adjust the nprocs value and set the appropriate values for open files. Current values can be checked by running “ulimit –a” command.

    Note:  Please ensure that the number of threads/processes that Java can spawn is high enough to ensure the number of java processes/threads running. In case of any “hangs”, please follow the link to capture the thread/heap dumps.
    000101754 - Remedy - Server - How to collect Java heap dumps (and thread dumps) for AR Server troubleshooting - ARS 9.x



    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles