Quantcast
Channel:
Viewing all articles
Browse latest Browse all 43889

Wiki Page: After rebooting the Application Server why does the performance seem slower in TMART Central 3.2 in comparison to version 3.0?

$
0
0
In TMART Central 3.2 an enhancement was implemented in order to improve overall performance; by caching measure objects such as names, id"s, data aggregation settings etc. The performance is improved by using the cached values; rather than querying the backend database when calculating the health for new Monitor results. However whenever the BMC Central Application server is shut down the cache will be lost and will therefore need to be rebuilt when the server is restarted. During the rebuilding process, the database will be busier and as a result the MeasureWrite time will increase and results may also be queued in the System Health tab. As a consequence you may therefore see slower performance in Central 3.2 after rebooting the Application server; however once the process of rebuilding the "cached values" is complete the overall performance of Central 3.2 should improve significantly.

Viewing all articles
Browse latest Browse all 43889

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>