Page tree

Unsupported content


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.

Skip to end of metadata
Go to start of metadata

The maximum best practice recommended capacity for a single BMC TM ART Central server is 350,000 measurements per hour, as identified on the Administration > System Health page in the BMC TM ART user interface. This capacity also assumes that:

  1. Both raw and 15-minute interval aggregate information is kept for less than 30 days.
  2. Data deletions are executed at least 2 or 3 times a week, or even daily.
  3. Online (that is, non-blocking) reindexing of indices for the SV_TimeSeriesData table is executed periodically as measure write time requires.
  4. Periodic reorganization of the SV_TimeSeriesData table is performed if this table becomes overly fragmented due to infrequent data delete executions under high volume.

For further information, see "Repository Maintenance" in the BMC Transaction Management Application Response Time Administration Guide.

In addition, the BMC ProactiveNet Server is limited in the number of monitors and attributes that it can process per time unit, regardless of their source (whether from the BMC TM ART Adapter or from any other adapter). You can use the following table and formula to estimate the number of monitors and attributes received from the BMC TM ART Adapter:

Monitor instance type (in hierarchical order)

Number of attributes per instance



   Project Monitor (multiple discovered)


      Location Monitor (multiple discovered)


         Transaction Monitor (multiple discovered)

Up to 126:

  • 6 static attributes
  • Up to 120 dynamic attributes
    • 50 custom timers (2 attributes per timer)
    • 20 custom counters (1 attribute per counter)


You can use filtering to reduce the number of discovered instances.

Total number of attributes per polling cycle = 5 x number of projects + 2 x number of locations + (6 + number of custom timers x 2 + number of custom counters) x number of transactions


  • Assuming BMC TM ART Adapter is collecting a total of 20 URL Checkers (with no custom timers), running on 50 locations and a single project: 5 attributes per project x 1 project + 2 attributes per location x 50 locations + 6 static attributes per transaction x 20 transactions = 225 attributes
  • Assuming the same numbers but with a custom transaction that has 50 timers and 20 counters: 5 attributes per project x 1 project + 2 attributes per location x 50 locations + (6 static attributes + [50 x 2] custom timers + 20 custom counters) x 20 transactions = 2625 attributes


If you are collecting historical datapoints from BMC TM ART Central, this value must be multiplied by the number of times (an integer) that the monitor execution interval fits into the polling cycle.

  • No labels