The Channel Backpressure Trap in .NET That Turns Small Spikes Into Memory Problems
Share

Our worker service looked fine at 9am. By 9:47 it had consumed 1.2GB of memory and the pod was restarting. No deployment. No config change…

 

<img src="https://cdn-images-1.medium.com/max/2600/0*wV8BNDbDRq9Ss7pQ" title="The Channel Backpressure Trap in .NET That Turns Small Spikes Into Memory Problems” /> Our worker service looked fine at 9am. By 9:47 it had consumed 1.2GB of memory and the pod was restarting. No deployment. No config change…Continue reading on Stackademic » Read More Dotnet on Medium 

#dotnet

By ali