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.
Any ideas @augustf?
Perhaps this needless alteration will help?
if ConcertoConfig[:autostart_delayed_job] == "true"
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.
Not starting delayed_job in test environment - perhaps helpful for #265
Assuming this works for your case, are there any initializers we should be doing this in?
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.