We're currently attempting to reduce the amount of memory used on the worker Dyno in Heroku.
As a first step, I'd like to propose checking the existence of the Subscription's course as the last filter before delivering the lesson. This is the most expensive call, and currently we're checking every active subscription before ensuring we're supposed to be sending it in the current window.
I think the next step will be to break this process up into multiple smaller jobs to parallelize this work.
We're currently attempting to reduce the amount of memory used on the
workerDyno in Heroku.As a first step, I'd like to propose checking the existence of the
Subscription'scourseas the last filter before delivering the lesson. This is the most expensive call, and currently we're checking every active subscription before ensuring we're supposed to be sending it in the current window.I think the next step will be to break this process up into multiple smaller jobs to parallelize this work.