New commit detected on ManageIQ/manageiq/darga: https://github.com/ManageIQ/manageiq/commit/8bb493c50efcdf121c10865c85cbc9c485949b18 commit 8bb493c50efcdf121c10865c85cbc9c485949b18 Author: Gregg Tanzillo <gtanzill> AuthorDate: Mon Jan 30 15:53:55 2017 -0500 Commit: Satoe Imaishi <simaishi> CommitDate: Tue Jan 31 08:50:17 2017 -0500 Merge pull request #12972 from Fryguy/move_vpor_creation_to_rollup_time Remove on-the-fly creating of VimPerformanceOperatingRanges (cherry picked from commit ff7a33b54006bcddeab9b0290495b2db58f9f92a) https://bugzilla.redhat.com/show_bug.cgi?id=1417662 app/models/metric/ci_mixin/long_term_averages.rb | 31 ++++--- app/models/metric/ci_mixin/rollup.rb | 7 +- app/models/vim_performance_operating_range.rb | 31 +++++-- spec/models/metric_spec.rb | 109 ++++++++++++----------- 4 files changed, 102 insertions(+), 76 deletions(-)
New commit detected on ManageIQ/manageiq/darga: https://github.com/ManageIQ/manageiq/commit/6839e65af07eb92678536844bbdf7e6fa9ac8017 commit 6839e65af07eb92678536844bbdf7e6fa9ac8017 Author: Gregg Tanzillo <gtanzill> AuthorDate: Mon Jan 30 17:57:28 2017 -0500 Commit: Satoe Imaishi <simaishi> CommitDate: Tue Jan 31 08:58:19 2017 -0500 Merge pull request #13700 from Fryguy/vpor_rollup_performance Only generate vpor for the TimeProfile specified, not all TimeProfiles (cherry picked from commit 9d4f10d6e9c3f76cdb51675560558ea9c7b0c15f) https://bugzilla.redhat.com/show_bug.cgi?id=1417662 app/models/metric/ci_mixin/long_term_averages.rb | 15 ++++++--------- app/models/metric/ci_mixin/rollup.rb | 6 +++--- app/models/time_profile.rb | 4 ++++ spec/models/metric_spec.rb | 14 ++++++++++---- spec/models/time_profile_spec.rb | 12 ++++++++++++ 5 files changed, 35 insertions(+), 16 deletions(-)
The code from the following PRs have been backported to DARGA: https://github.com/ManageIQ/manageiq/pull/12972 https://github.com/ManageIQ/manageiq/pull/13700 And have reduced the strain on these types of reports. Future improvements will made in the newer releases since we can make use of refactorings that will allow us to make further performance improvements on top of what we are doing here.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0474.html