If it takes t seconds to read a default-config-variable, and we have n config-variables, then me solution would take t*n seconds. Your solution would take t*n seconds for each varaible, what is t*n*n → t*n² seconds. If t is very small, there should be no big difference. But If your solution has no other benefit, even a small performance boost is better.

And you are wrong, not the hole cache-object has to be read again, but only one value from it. If you want to read the value 'openslides', python generate the hash from this string
```python
hash('openslides')  # == 4452773352864541572
```
Then it looks in the config-object only for this value. This is really fast and don't has to touch any other entry in the dictionary.

I can't see neither, why the developer has to pay attention about the cache?