I tried that way but

1. it is difficult, in the sense that we cannot pass to celery Django objects, apparently they are not pickeable
2. it would not save any significant time since at the moment the worker is doing much more work to save the distribution (one query per asset per damage state) than to retrieve the available damage states.

It is possible that the db is a bottleneck here, but then we will have to do something smarter than just passing the damage states; I would leave this open for the future (we will do some profiling/optimization at some point).