Asynchronously load next records in ActiveRecordCursor #344
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It occurred to me the other day that Job Iteration could benefit from Rails 7's async queries. Whilst the job is doing HardWork™️ in
#each_iteration
, we can begin fetching the next batch of records on another thread. Although most query times are probably < 100ms, this does add up for a job performing thousands or millions of iterations.Example
I've given this branch a spin locally with a slow job & query:
With async loading (note 1 second between printed times):
Without async loading (approx. 2 seconds between printed times):
In this contrived example the total time to iterate over 112 records was ~58s with async, ~113s without async.