Project

General

Profile

Actions

Bug #14503

closed

Listing reports for a host via API/hammer consumes large amount of memory

Added by Ivan Necas about 8 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Performance
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #10053: Table lock hangs all processesClosedMarek Hulán04/07/2015Actions
Actions #1

Updated by The Foreman Bot about 8 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/3394 added
Actions #2

Updated by Ivan Necas about 8 years ago

  • Related to Bug #10053: Table lock hangs all processes added
Actions #3

Updated by Marek Hulán about 8 years ago

  • translation missing: en.field_release set to 136
Actions #4

Updated by Ivan Necas about 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #5

Updated by Dominic Cleal almost 8 years ago

  • Category set to Performance
Actions

Also available in: Atom PDF