Bug #14503
closedListing reports for a host via API/hammer consumes large amount of memory
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1324461
Description of problem:
Depending on the size of reports for a host, the request for the reports
for a host via API/hammer consumes large amount of memory.
How reproducible:
the system needs to have reasonable history of puppet reports in order to reporduce the issue
Steps to Reproduce:
1. curl -k -u admin:changeme -H "Accept:application/json"\
https://foreman.example.com/api/v2/hosts/myhost.example.com/reports?per_page=120
Actual results:
The passenger process starts consuming a lot of memory and it takes tens of minuts to finish (if the server doesn't fail on insufficient amount of memory before it finishes).
Expected results:
The request returns reports for a host
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3394 added
Updated by Ivan Necas over 8 years ago
- Related to Bug #10053: Table lock hangs all processes added
Updated by Marek Hulán over 8 years ago
- Translation missing: en.field_release set to 136
Updated by Ivan Necas over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset aeba4f428494f2ee3aedf18088561c23c4407309.