Better support archived records in VimPerformanceStates

[kbrock]

The goal is to reduce the overhead of archived records when working with VimPerformanceStates

• remove extra vim_performance_state finders #22580
• Only load performance states for the records of interest  #22579
• VimPerformanceState#purge_timer for old records #22605
  • Purge dated VimPerformanceStates #11868
• Specs for Vim Performance States #22607
• Precache rollup values #22594
  • rollup_child_metrics: preload containers#container_image (child -> parent)
  • clean out container_image#containers from when creating vps. (will use vps to lookup up association, so is wasted memory)
  • object association is still in memory (ContainerImage#containers) may want to reset the association.
• (fixes bugs in previous) Precache rollup values #22604
• Vim performance state time interval #22606
• VimPerformanceState#vim_performance_state_for_ts optimizations #22611
  • state_finders: 25 doesn't cache newly created states, so we look it up instead
• VimPerformanceState do not bring back archived records #22589
  • keep states as is but instead just trim the id list of containers to ones that are active
• Shorten the query for pre-loading VimPerformanceStates #22648
• Metric::Rollup - simplify column declarations #22608
• Keep archived out of VimPerformanceState #22585

next phase:

• [WIP] Only collect rollup associations #22609
  • VimPerformanceState#associations - only store the associations that are needed
• VimPerformanceState cleanup: prune invalid ids, deleted_on, and possibly unneeded ASSOCIATIONS values

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

[Fryguy]

@kbrock Since most of this is done, should we close this as completed? Or do we need to wait for the rest of the checklist?