Created attachment 1221245 [details] exported yaml file of custom report consuming too much time and resource Description of problem:Customer has created a specific report to execute in their global VMDB which is intended to report on entire estate of VMs in the environment. It has been necessary to increase the memory_threshold significantly (from 600 MB to 2500MB) and to increase the reporting timeout value from 3600 seconds to 7200 seconds to allow the report to reliably complete. Version-Release number of selected component (if applicable):5.6.1.2 How reproducible:need to run specic report (ymal file attached) in an environment with > 25k VMs. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
PR used (of many) https://github.com/ManageIQ/manageiq/pull/12733
PR: https://github.com/ManageIQ/manageiq/pull/12911
This has mostly been addressed in the cloned BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1417662 But these are the PRs that have been merged and will be made available in both 5.7 and 5.8: https://github.com/ManageIQ/manageiq/pull/12972 https://github.com/ManageIQ/manageiq/pull/13700 https://github.com/ManageIQ/manageiq/pull/13101 With the 3 of these in place, we should expect to see the report generate 90% faster, and with a much lower memory footprint (less is being downloaded from the database, resulting in both speed and memory efficiency).
the original backup file is being restored to the originally indicated location. As before, it is still about 12 GB. The restore should be complete by 11:00 AM April 27,2017. location: http://file.rdu.redhat.com/~thenness/SF-01738251-db