I've been pulling out my hair on this one. I have a dotnet core(3.1) service deployed in a swarm of 3 workernodes, on each node I have a web api that uses redis for various things. The redis server itself never is busy, and the cpu rarely exceeds 4%, but my web api's cpu usage is quite high (~60% average). I used dotnet trace to check what's eating my cpu and found 
All work seems to go to the thread pool scheduler used by StackExchange.Redis. I'm only reusing 1 ConnectionMultiplexer and stored it in a singleton as recommended. I've tried StackExchange.Redis 2.1 as well as the latest version, but that doesn't seem to make a difference.
Can anyone pinpoint me to what might be wrong here?