Admin system configuration slowdown when saving config value about magento2-sentry HOT 2 CLOSED

Me too, I've done my Blackfire profiling and it's a deadlock.

Cache->flush will rebuilt the cache which locks the cache until it's written and it also writes something to the log..

The log where Sentry gets injected wants to check if Sentry is enabled in config, so it triggers a cache->load which is of coarse locked, which results in a deadlock.

I would suggest, having that Sentry is a debug tool that we'll move to environment variables via app/etc/env.php

Another solution would be to built a configuration object during bootstrap events in Magento which will be used the rest of that code execution.

Related Magento code magento/magento2@0461b07

They lock the cache because creating the cache takes time, so if a lock is set, all other processes wait for the locker until it's finished creating the cache, usually ~2 seconds. Magento checks every 100ms if the lock is removed, and for a maximum of 42 seconds.

Magento could also resolve this during build of new cache, and only locking during the replace action. And also internally return old stuff in the read, and after save returning the new stuff.

from magento2-sentry.

The PR is merged, thanks for contributing to this issue.

from magento2-sentry.