I am not sure that is so. I have experience with one system under load when about 20k `conj_keys` had been invalidated at one moment. In that moment 1500 uwsgi-workers (readers) smoked about several seconds while waiting for Redis. Thus all `world` had stopped and service was interrupted. It happened because current version of invalidation contains one long transaction (aka lock) for readers and writers. I will provide more explanation of my thoughts in comments below.

But in any way, thank you, that you noted this line. I will measure and compare it with current version.