Closed Bug 531944 Opened 15 years ago Closed 15 years ago

[AMO] Update cron on preview

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

All
Other
task
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jbalogh, Assigned: fox2mike)

Details

Please change "/usr/bin/python26 build-recommendations.py" to "/usr/bin/python26 build-recommendations.py addons".  It keeps the same timing.

Then add a new one:

    /usr/bin/python26 build-recommendations.py collections

This takes over 45 minutes (!) to run on khan, but only needs to run once per day (or less).  All of the time is spent doing calculations on in-memory data, so it shouldn't tie up the db.  It doesn't take up a whole lot of memory (1.5% * 4051M = 60M on khan), but it will peg the cpu core it's running on.
a=clouserw

I don't think CPU is a big deal so I'm fine with once a day but if you're concerned about it we can space it out further too.  Also, I'd be interested in how fast it runs on the real box.

This is filed as minor but it does block QA and our push is next week so I'll bump it up as we get closer if it's still open.
Assignee: server-ops → shyam
Done. The new one runs at 1630 PST every day. If it really causes issues (CPU wise) we'll find out fairly quickly.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Wil, how does this block QA?
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.