See http://docs.celeryproject.org/en/latest/userguide/optimizing.html#using-transient-queues
Since we don't need persistence in redis (both for cache and broker) I suggest doing this.
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
This has already been implemented (albeit not in celery but redis). https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/394022/2/modules/ores/manifests/redis.pp
I am unsure about losing the contents of the entire cache every time redis/the machine is restarted. We can however simulate that in say labs to get an idea of the repercussions.