Bug 6523 - Look into RAM usage
Summary: Look into RAM usage
Status: RESOLVED FIXED
Alias: None
Product: Error Reporting tool
Classification: Yocto Project Subprojects
Component: Error Reporting Tool (show other bugs)
Version: 1.7
Hardware: All Multiple
: Low enhancement
Target Milestone: 1.8 M2
Assignee: Michael Wood
QA Contact:
URL:
Whiteboard: GUI design available
Depends on: 6873 6875 6876 6877 6878
Blocks:
  Show dependency tree
 
Reported: 2014-07-11 08:58 UTC by Belen Barros Pena
Modified: 2015-01-23 19:54 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Design - Show older errors (529.96 KB, application/pdf)
2014-10-09 11:23 UTC, Belen Barros Pena 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Belen Barros Pena 2014-07-11 08:58:36 UTC 
The server hosting the errors tool has been throwing out of memory errors. Michael Haldstead has increased the machine memory, but RP thinks we should look into the tool to see why it is so RAM-hungry.
Comment 1 Belen Barros Pena 2014-07-15 14:09:20 UTC 
RP has recommended maybe returning only the latest 200 bug entries for any given set of search results.
Comment 2 Mark Hatle 2014-07-16 14:51:07 UTC 
RPM (5) uses berkley DB for the database.  Most of the memory used by RPM is configured in the Berkley DB config file var/lib/rpm/DB_CONFIG.
Comment 3 Mark Hatle 2014-07-17 14:34:57 UTC 
(ignore comment 2 -- I got this confused with a different bug)
Comment 4 Belen Barros Pena 2014-10-09 11:23:11 UTC 
Created attachment 2174 [details]
Design - Show older errors
Comment 5 Belen Barros Pena 2014-10-09 11:23:54 UTC 
(In reply to comment #1)
> RP has recommended maybe returning only the latest 200 bug entries for any
> given set of search results.

If we do this in the end, we should probably provide an option to show older errors. I've attached a design document for this.
Comment 6 Michael Wood 2014-10-20 19:00:40 UTC 
Currently working on this and other issues which are coming up at in a branch michaelw/master in the error-report-web repo
Comment 7 Michael Wood 2015-01-23 19:54:01 UTC 
Should be fixed by

commit 1d001145096082f7d10e66fde8a1fa1706f515c9
    Move the filtering, queries and ordering to use the orm functions
    
    - Rewrite the main views so that all the data manipulation is done in the
    database rather than in python. This was causing large performance
    issues.