Closed Bug 1182581 Opened 9 years ago Closed 9 years ago

Memory quota exceeded for hourly update

Categories

(Webtools Graveyard :: Pontoon, defect)

Product:
Webtools Graveyard
Component:
Pontoon
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox42 affected)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox42 --- affected

People

(Reporter: osmose, Unassigned)

Details

In Papertrail we're seeing a bunch of error messages about exceeding our memory quota in dynos set up by Heroku Scheduler, which runs the hourly string update:

> Jul 10 06:26:00 mozilla-pontoon heroku/scheduler.1317: Error R14 (Memory quota exceeded) 

I've upgraded to a 2x dyno for the job but I suspect there's several optimizations to be made for update_projects and commit_projects.

It'd be nice if we could get a performance profile of what's happening during the scheduled job to know what needs to be knocked out first.
Can't see any trace of Memory quota exceeded in the last few days. Shall we close this one and continue sync optimization discussion in bug 1191718?
Sure!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.