Open Tvde1 opened 1 year ago
I think 'conn-sec' is about the duration of your current connection. check this out would you plaese share more details of the way you are using SE.Redis ? Maybe you're in a high load condition? Do you have any concurrency handling mechanisms ? Are you sure that you do not have network issues ?
'WORKER: (Busy=5,Free=32762,Min=4,Max=32767)' indicates that you have more Busy threads than the Min thread pool size, which means you're experiencing thread pool throttling. You'll want to ensure all your calls into SE.Redis are using the *Async() methods and/or increase the Min thread pool size. More details in https://stackexchange.github.io/StackExchange.Redis/Timeouts
All calls are awaited. Is it possible that this happens when you just do too many redis calls? Will up the min thread pool for sure
@Tvde1 Didn't see the follow-up here is it possible the HMGET
is getting a rather large number of keys here?
Hi, for a while now we have started seeing some very slow calls, and the profiler in our Azure App Service shows us it's due to awaiting in Stackexchange.Redis:
I'm unsure about how often this happens, We are on:
I have also caught several RedisTimeoutException
This shows the
conn-sec: 53289.39
being very high, and not necessarily a lack of worker threads.I'm not even sure if these two problems are related to the same root cause.
What can I do to investigate this issue better?