Terracotta Ehcache 10.7 | Terracotta Management and Monitoring | Performance Considerations
 
Performance Considerations
The TMC application being both a statistics database and an application server on the same process, we strongly advise you to allocate at least 2GB of offheap memory (tms.offheapSizeMB=2048). Also, this memory amount will depend on how many statistics are stored and whether the persistence mode is INMEMORY or HYBRID (see below).
The amount of statistics the TMC can store depends on the number of objects in your cluster (not the number of clients). The more objects (caches or datasets) in your clients, the more memory/disk the TMC internal datastore will require.
For example, with the following configuration and a collector interval set to 30 seconds, and a cluster of 60 objects (mix of datasets and caches), the TMC's offheap memory will typically grow about 180MB per hour.
tms.offheapSizeMB=2048
tms.persistenceMode=INMEMORY
There are several parameters you can control depending on your cluster size and the quantity of history you want to keep.
*Collector Interval: In TMC, this controls how frequently the statistics will be collected and stored in the TMC database.
*tms.persistenceMode: INMEMORY will keep all the data in offheap memory (and disk). This speeds up the queries but requires a lot of memory if you want to keep a large history. HYBRID will keep only the indexes in memory. The query speed will depend on the disk speed.
*tms.offheapSizeMB: This controls the maximum offheap memory allowed for the TMC. HYBRID requires less memory than INMEMORY.
*tms.offheapThreshold: This is the threshold (as a percentage of tms.offheapSizeMB) above which the TMC will remove the oldest statistics from the database. This purging process is required so that the TMC does not run out of memory. 80% is a good value for 2GB of offheap memory when using INMEMORY.
*tms.statisticsMaxAgeMinutes: This parameter controls the maximum time (in minutes) the statistics will remain in the database. Statistics stored before this delay get removed. This parameter has an effect on the time frames you will be able to see in the TMC UI, assuming you have enough memory and/or disk space to store the statistics for this period of time.