NetCoreServer icon indicating copy to clipboard operation
NetCoreServer copied to clipboard

Memory Management Question

Open stevozilik opened this issue 3 years ago • 0 comments

Hi,

I'm looking to upgrade some older .Net Framework TCP server framework. I remember at the time (and possibly still), the biggest challenge I had was memory leaks, and CPU consumption.

At the time Tasks were a new thing and the recommendation was to utilise patterns like SocketAsyncEventArgs to improve both memory and CPU, although I still think it's leaking.

Ultimately some of it was down to Windows OS unmanaged memory pinning/fragmentation, which I never really solved.

What's the situation these days, and I guess specifically with this library in regards to Memory Management/leaks. How much is 'taken care of' by the framework, and what can consumers do to avoid memory leaks (could not see anything in the documentation)?

Kind regards, Stefan

stevozilik avatar Oct 22 '20 18:10 stevozilik