David Gobaud

Would be good to be able to say the fee is not modifiable so people don't worry about you setting the fee to 100% etc later

There actually might be some compliance costs for some security tokens when they move between different owners - a transfer agent might charge based on number of exchanges etc

Supporting all 4 of those options would be great and letting the issuer configure it

what is the dj binary/does it cover the issue in https://github.com/collectiveidea/delayed_job/pull/565 ?

but those don't support NUM_PROCESSES for running multiple workers on a single dyno correct?

Got it - I understand it doesn't make sense to include if it causes problems. What are the problems/bugs? I'd like to fix them if possible.

Sounds good. I've made all the changes except "Cleanup forked workers on exit" - I'm not sure how best to do that.

I'm still seeing this problem and I have cache_classes set to true ruby '2.2.2' gem 'rails', '4.2.5' delayed_job (4.0.6) delayed_job_active_record (4.0.3) It's just a steady march up...  

I don't think my jobs consume a lot of data (or use a lot of memory I guess is what you mean?) but I have a lot of jobs... I...

I'm still seeing this problem and I have cache_classes set to true ruby '2.2.2' gem 'rails', '4.2.5' delayed_job (4.0.6) delayed_job_active_record (4.0.3) It's just a steady march up...