This documentation supports the 9.1 version of Remedy IT Service Management Suite.

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

Sizing baselines

This topic describes the BMC Remedy IT Service Management (ITSM) Suite deployment architecture and includes the following:

 

Environment baseline guidelines

The sizing baselines in the following table are based on performance lab benchmark tests and examples observed from consulting services and customer experience. The following are the branchmark scenarios and their definitions.

  • Concurrent users is used to estimate the number of simultaneous connections to the mid tier or BMC Remedy AR System servers. If your organization is using a significant number of web-based clients (utilizing the mid tier) and the thick-based BMC Remedy client tool, you should calculate the totals for each and use the total number as the estimate for concurrent users.
  • The term managed device has historically referred to devices that have an IP address and can therefore be remotely connected to over an Ethernet network. However, this might not always be the case. It might be beneficial to track other items as well. BMC Atrium CMDB enables you to track items that do not have an IP address, such as telecommunication network links (T-1s, DS3s, and so on) or desk telephones that can be tracked another way, such as through MAC addresses or serial numbers.
EnvironmentBMC Remedy ITSM
(concurrent users)
BMC Remedy Smart Reporting (concurrent users) Maximum number of managed devices*

Proof of concept (POC)

50

5

1,000

Small

800

50

2,000

Medium

2,000

100

10,000

Large

5,000

250

30,000


Hardware recommendation

Click here to download a VSDX file (Microsoft Visio 2013) that contains a source copy of this diagram that you can customize to your environment. The following architecture diagram displays specifications for deployment on separate servers that are logically connected; and is applicable for a medium-sized environment.

 

Note

Use the following size estimates as guidelines. Conduct benchmarks in your environment to get accurate sizing based on your workload mix, data volumes, and date composition.

ComponentPOCSmallMediumLarge

BMC Remedy AR System mid tier servers

None: Services combined with AR System server

Two servers:

2 CPU core
8 GB RAM
120 GB disk space

Two servers:

4 CPU core
12 GB RAM
120 GB disk space

Five servers:

4 CPU core
16 GB RAM
120 GB disk space

BMC Remedy AR System Web Services

None: Services combined with AR System server

One server:

2 CPU core
8 GB RAM
60 GB disk space

One server:

4 CPU core
8 GB RAM
60 GB disk space

Two servers:

4 CPU core
8 GB RAM
60 GB disk space

BMC Remedy Single Sign-onNone: Services combined with AR System server

One Server:


2 CPU core
8 GB RAM
200 GB disk space

Two Servers:


2 CPU core
8 GB RAM
200 GB disk space

Four Servers:


2 CPU core
8 GB RAM
200 GB disk space

BMC Remedy Smart ReportingOne server: 

2 CPU core 
12 GB RAM
60 GB disk space 
One server: 

4 CPU core 
12 GB RAM
200 GB disk space

Two server:

4 CPU core 
16 GB RAM
200 GB disk space

Two servers: 

8 CPU core 
32 GB RAM
200GB disk space

BMC Remedy AR System server (user-facing)
BMC Atrium CMDB
BMC Remedy ITSM
BMC Service Level Management
BMC Service Request Management
 BMC Knowledge Management

User-loaded servers

One server:

4 CPU core
12 GB RAM
120 GB disk space

Two servers:

2 CPU core
12 GB RAM
120 GB disk space

Three servers:

4 CPU core
16 GB RAM
120 GB disk space

Four servers:

8 CPU core
32 GB RAM
120 GB disk space

BMC Remedy AR System server (back end)
BMC Atrium CMDB
BMC Remedy ITSM
BMC Service Level Management
BMC Service Request Management
 BMC Knowledge Management

Non-user-loaded servers for back-end BMC Remedy AR System processes, integrations, reconciliations, and notifications

One server:

4 CPU core
12 GB RAM
120 GB disk space

Two servers:

4 CPU core
12 GB RAM
120 GB disk space

Two servers:

4 CPU core
16 GB RAM
120 GB disk space

Two servers:

8 CPU core
32 GB RAM
120 GB disk space

BMC Remedy with Smart IT and BMC MyIT

None: Services combined with AR System server

One server:


4 CPU core
12 GB RAM
200 GB disk space

Two servers:


4 CPU core
16 GB RAM
200 GB disk space

Three servers:


8 CPU core
16 GB RAM
200 GB disk space

The sizing specification is for each server or node in a cluster.

 Other deployment sizing considerations

  • BMC Virtual Chat is deployed on the same Tomcat server on which  the BMC Remedy Mid Tier is installed.
  • BMC Remedy Single Sign-On can be deployed on the same Tomcat server on which the BMC Remedy Mid Tier is installed. Ensure that the system has adequate resources to support both the applications.
  • A typical MongoDB server requires a three-node deployment: one primary and two secondary. Another option is to deploy MongoDB using two servers: one primary and one secondary, with an arbiter on one of the Smart IT-MyIT servers.

Hardware considerations for data

  • The Atrium Web Registry database is not transactional in nature and therefore much smaller in size. For small, medium, and large deployments, this database can be installed on the same Microsoft SQL Server instance.
  • The sizing in the preceding table is based on benchmark tests for specific use cases only.
  • Transaction log sizing is mainly driven by the following factors. BMC recommends sizing the transaction log files based on these factors:
    • Database recovery model
    • Database backup strategy and frequency

Database tier sizing recommendation

The following disk sizes indicates the disk space that is occupied by data and indices. Always include additional space for additional data, OS, and any other additional software installed.

Use the following size estimates as guidelines. Conduct benchmarks in your environment to get accurate sizing based on your workload mix, data volumes, and date composition. Download a copy of the planning spreadsheet.

Component

POC

Small

Medium

Large

Master BMC Remedy AR System Database

1 server:

4 CPU Core
8 GB RAM
100 GB disk

One cluster:

8 CPU Core
16 GB RAM
200 GB disk

One cluster:

16 CPU Core
32 GB RAM
200 GB disk

One cluster:

32 CPU Core
64 GB RAM
200 GB disk

Replicated BMC Remedy AR System Database for Reporting

None: Services combined with AR System database

One server:

8 CPU Core
16 GB RAM
200 GB disk

One server:

16 CPU Core
32 GB RAM
200 GB disk

One server:

32 CPU Core
64 GB RAM
200 GB disk

Mongo DB (social database for Smart IT and MyIT)--

3-node MongoDB replica set cluster:

2 CPU core
8 GB RAM
150 GB SSD (Mongo 3.x WiredTiger)

3-node MongoDB replica set cluster:

4 CPU core
12 GB RAM
200 GB SSD (Mongo 3.x WiredTiger)

3-node MongoDB replica set cluster:

4 CPU core
16 GB RAM
500 GB SSD (Mongo 3.x WiredTiger)

Java heap size recommendation

The following Java heap size requirements are only guidelines. Adjust your Java heap size based on your load conditions. The heap size is set in the arserver.config file (Windows) or arserverd.conf file (Linux or Solaris) located in the ARSystem directory.

 jvm.maximum.heap.sizeConcurrent users Memory size
Medium 8589934592 800–2,000 16 GB
Large21474836480 2,000–5,000 32 GB

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

Additional JVM garbage collection (GC) parameters

jvm.option.[xx]=-XX:+UseConcMarkSweepGC 
jvm.option.[xx]=-XX:+UseParNewGC 
jvm.option.[xx]=-XX:+UseCompressedOops 
jvm.option.[xx]=-XX:NewRatio=2 
jvm.option.[xx]= -XX:+HeapDumpOnOutOfMemoryError 
jvm.option.[xx]= -XX:HeapDumpPath=<Path> 
jvm.option.[xx]= -XX:ErrorFile=<Path>\hs_error_%p.log 
 

For information about adding these parameters, see  KA000113248 .

How BMC develops deployment recommendations

The BMC Performance Lab conducted a set of online and batch workloads to benchmark the performance and scalability of the BMC IT Service Management Suite and to characterize the system behavior under various workload conditions. The supporting environment and IT infrastructure used for these workloads were constructed to reflect the typical deployment architecture. For more information, see  2019-01-22_00-11-16_Benchmark summary.

Related topics

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Steven Casey

    Where are the sizing baselines?

    Feb 03, 2016 12:24
    1. Amit Durgapal

      Hello Steven,

      Sorry about responding late. The sizing baselines are detailed at Hardware requirements .

      Regards,

      Amit

      Apr 22, 2016 01:59
  2. Thomas Rã¶ttig

    This article states under Hardware Recommondations that there is a link to download the visio file but there is no file linked currently.

     

    Feb 21, 2017 10:20
    1. Mokshada Shivarekar

      Hello Thomas,

      The Visio file is linked under the Hardware Recommendations.

      Thanks and regards,

      Mokshada

      Mar 02, 2017 03:39
  3. Thomas Rã¶ttig

    Hi Mokshada

    If I use the link above, I just end up on this same page again.

    Regards,

    Thomas

    Mar 02, 2017 05:35
    1. Priya Shetye

      Hello Thomas,

      Mokshada has updated the file on the page. You should now be able to download the visio file.

      Regards,

      Priya

      Mar 03, 2017 03:44
      1. Thomas Rã¶ttig

        Hi Priya

        Works now....

        Tnx

        Thomas

        Mar 03, 2017 09:43
  4. Mpumelelo Tsabedze

    Good Day,

     

    May you please advise if the Integration, RSSO and Admin Application server cluster is in its own server group separate from the Customer facing Application server group ?

    If so, would this entail putting a vip between the 2 Admin app servers ?

    Apr 06, 2017 09:37
    1. Mokshada Shivarekar

      Hello,

      Thank you for inquiring. I will work on this and get back to you.

      Regards,

      Mokshada 

      Apr 06, 2017 10:44
      1. Mpumelelo Tsabedze

        Hi Mokshada,

         

        Have you managed to come back with anything on this ?

        Its been a while since no response

        Tx

        Mpumi

        Jun 07, 2017 10:43
        1. Jyoti Nerkar

          Hello Mpumelelo,


          Sorry for delay in reply. The answer to you query 'if the Integration, RSSO and Admin Application server cluster is in its own server group separate from the Customer facing Application server group ?' is YES.


          Hope this helps.

          Jyoti

          Jul 03, 2018 01:11
  5. Chris Parent

    Under database sizing estimates can you provide numbers for:

    1) SMART-IT database (not the social/Mongo DB).

    2) SMART Reporting database

    Both of those installers create database instances.

    Jun 07, 2017 10:33
    1. Nidhi Das

      Hello Chris,

      I will discuss this with the concerned SME and will update the topic.

      Thanks,
      Nidhi

      Jun 08, 2017 01:35
    1. Nilay Agambagis

      Hello Chris,

      Thanks a lot for your comment.

      Please check the links below for Smart IT performance related information:

      Smart IT 1.6: https://docs.bmc.com/docs/display/smartit16/Smart+IT+1.6+performance
      Smart IT 2.0: https://docs.bmc.com/docs/display/smartit20/Smart+IT+2.0+performance

      Regards,

      Nilay Agambagis

      Sep 05, 2019 05:47
  6. Andree Laliberte

    Do you consider development environment as a POC for sizing? There is not information about MongoDB placement an sizing for a POC here but in the installation instructions for SmartIT you recommend to install a single server for the MongoDB database. What should be the sizing for this database in a development environment with no more than 20 concurrent users.

    Jan 18, 2018 08:55
    1. Mokshada Shivarekar

      Hi Andree,

      I will discuss this with the concerned SME and write back to you.

      Thanks,

      Mokshada

      Jan 18, 2018 10:17
  7. Andree Laliberte

    Since MongoDB is no longer needed, is it possible to have and update on the sizing guidelines :

    MongoDB no longer required to support Smart IT social features

    As part of the Smart IT architecture simplification enhancement, starting with Smart IT 18.05, MongoDB installation is not required. MongoDB is no longer required to support Smart IT social features. All your social data is now stored in the AR System database forms.

    Before you upgrade to Smart IT 18.05, if you need to retain your old social timeline data, migrate your social data from MongoDB to the AR System database using the mongo migration utility. For more information, see Migrating social data from MongoDB to the AR System database.

    Jul 03, 2018 11:35
  8. Ricky R

    hi BMC,

    Can anyone explain what is mean by the 'Maximum number of managed devices' column means? is it means the CMDB CI container maximum records or is it means the number of devices which can connect to remedy as same time?

    Regards, Ricky

    Jun 26, 2019 07:56
    1. Himanshu Raul

      Hi Ricky,

      Thank you for your comment. The term 'Maximum number of managed devices' refers to both:

      1. the number of devices (having an IP address) connecting to Remedy ITSM Suite

      and

      2. the assets data present in the CMDB CI (CMDB CI container maximum records).

      Regards,

      Himanshu

      Jul 05, 2019 01:19