Delayed Job Storm #265

Closed
bamnet opened this Issue Dec 19, 2012 · 5 comments

Projects

None yet

2 participants

@bamnet
Concerto Digital Signage member

Delayed job seems to be spinning up a lot of processes eating a lot of memory and CPU. This might be related to the work in 6ecea55 which auto-started delayed job.
dj

@bamnet
Concerto Digital Signage member

Any ideas @augustf?

@augustf
Concerto Digital Signage member

Perhaps this needless alteration will help?

unless daemon_is_running?
if ConcertoConfig[:autostart_delayed_job] == "true"
start_delayed_job
end
end

@augustf augustf was assigned Dec 19, 2012
@bamnet
Concerto Digital Signage member

I bet this initializer is run everytime the test suite is started, can we disable that? Delayed job should never boot automatically in a test environment.

@augustf
Concerto Digital Signage member

Assuming this works for your case, are there any initializers we should be doing this in?

@bamnet
Concerto Digital Signage member

Taking a look at the list, I don't see anything else dangerous. Airbrake is configured to only listen in production, and the migration one shouldn't do anything that the test env doesn't already.

I think this is fixed, will reopen if I find otherwise.

@bamnet bamnet closed this Dec 20, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment