Jon McKenzie
- Login: jcmcken
- Email: jcmcken@gmail.com
- Registered on: 07/01/2013
- Last sign in: 08/17/2016
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 2 | 2 |
Reported issues | 0 | 7 | 7 |
Activity
08/24/2016
- 05:43 PM Foreman Bug #9016: Fact import code consumes lot of memory
- Lukas Zapletal wrote:
> > Changing this on L.81 in your referenced PR...
>
> Actually, I completely removed the l...
08/22/2016
- 01:15 PM Foreman Bug #9016: Fact import code consumes lot of memory
- Changing this on L.81 in your referenced PR......
08/19/2016
- 10:04 AM Foreman Bug #9016: Fact import code consumes lot of memory
- Hi Lukas,
I can tell by reading this code that this isn't going to solve our issue, or at the very least will caus...
08/18/2016
- 11:02 AM Foreman Bug #9016: Fact import code consumes lot of memory
- We ended up having to patch the fact importer code on all of our Foreman app servers. This could probably be a bit mo...
08/17/2016
- 06:43 PM Foreman Bug #9016: Fact import code consumes lot of memory
- Just chiming in here. The current fact importer (we use 1.10, but it seems similar in 1.11 and 1.12) creates a huge p...
05/20/2015
- 07:25 AM Foreman Revision 5b7ac025 (foreman): Fixes #5568 - Improves performance of trends:clean rake task
- Perform trend counter dupe counting within the database rather than in the Ruby code.
(cherry picked from commit 040...
05/13/2015
- 04:01 AM Foreman Bug #5568 (Closed): Possible memory leak in trends
- Applied in changeset commit:040abfa32f326de7cd488f34f243377f76fd70ae.
- 03:25 AM Foreman Revision 040abfa3 (foreman): Fixes #5568 - Improves performance of trends:clean rake task
- Perform trend counter dupe counting within the database rather than in the Ruby code.
05/12/2015
- 06:34 PM Foreman Feature #7033: Syslog capability
- If this capability were developed, would it be included with Foreman or be pushed into a plugin (can a Rails engine r...
05/09/2015
- 02:47 PM Foreman Bug #5568: Possible memory leak in trends
- Huh, I must have misread this issue initially, which is for @trends:counter@ not @trends:clean@. Oh well, I submitted...
Also available in: Atom