It would be awesome if linter could warn user on every config.no_cache =1 usage.
Instead of setting setting config.no_cache one should use USER_INT.
using config.no_cache is 5x slower than USER_INT (in scenarios where multiple concurent request are comming). This is due too fact that no_cache is locking cache for writing, but at the end no cache entry is generated, so multiple requests are waiting on each other.
martin-helmich
commented
3 years ago
It would be awesome if linter could warn user on every
config.no_cache =1usage. Instead of setting setting config.no_cache one should use USER_INT. using config.no_cache is 5x slower than USER_INT (in scenarios where multiple concurent request are comming). This is due too fact that no_cache is locking cache for writing, but at the end no cache entry is generated, so multiple requests are waiting on each other.