Description of problem:
I introduced the metrics_cache table in RHQ 4.12 as a way to reduce queries required during metrics data aggregation. This was intended as a performance optimization. It is described at https://docs.jboss.org/author/display/RHQ/Aggregation+Schema+Changes. I have learned in part from community feedback (i.e., Elias Ross), that the gains are often minimal because there are not tight groupings of schedule ids. 

More importantly the new table causes higher heap usage which can result in lots of alert notifications especially for default installations. This could be problematic for a lot of users who run only a single, co-located storage node along side the server. We are better of dropping the table. I think rhq-metrics would be a more appropriate place to explore changes like this.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: