In the spirit of #1519 -- it can be helpful in some environments to cache results and then do a batch update.
Specifically for preprocessing, jobs are performed without holding a "lock" on a db row -- so just caching and applying a bunch of state updates would be sufficient.
Similar cache would be useful for obsdb ... this could be very similar to the thing in #1519 -- maybe even a general thing might handle both cases.
In the spirit of #1519 -- it can be helpful in some environments to cache results and then do a batch update.
Specifically for preprocessing, jobs are performed without holding a "lock" on a db row -- so just caching and applying a bunch of state updates would be sufficient.
Similar cache would be useful for obsdb ... this could be very similar to the thing in #1519 -- maybe even a general thing might handle both cases.