BMC Support and Engineering team worked together with few customer cases lately for Remedy 9 version. These cases were reported within performance and stability portion of the functionality. Upon reviewing/analysing series of logs data and troubleshooting it precisely, we (BMC) have come up with following recommendation that should help mitigate the maximum performance issues.
1. Run the config-checker tool post 9.1 upgrade/install and address anything that is flagged
This tool gives information about what is current setting/configuration on Remedy AR System/Database/Operating System etc. As a result of this tool execution, this also offers best possible setting that you can configure for Remedy 9.
2. Configure Database Parameters:-
Set Cursor Sharing in DB 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 here:
Set "_b_tree_bitmap_plans" to FALSE in the database
- Set the READ_COMMITTED_SNAPSHOT to ON
- Set the PARAMETERIZATION to SIMPLE
MS-SQL Parameters have been documented here:
3. Apply the most current hotfix package for the server and midtier (If server group then on all servers)(ftp://ftp.bmc.com/pub/ARRecommendedFixes/)
4. For Medium size environments with 800-2,000 concurrent users and 16 GB RAM, set jvm.maximum.heap.size to at least 8589934592. For a Large environment (2000-5000 concurrent users and 32 GB RAM) set jvm.maximum.heap.size to at least 21474836480.
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
See https://docs.bmc.com/docs/display/public/brid91/Hardware+requirements for more details.
Add additional garbage collection parameters:
Check the article: 000113248 to know the required steps to set these values.
5. If using Linux:
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.
Message was edited by: Kiran Hullule