4 ms·
Back in 2005-2006 we ran into significant issues with the GC and pinned memory related to Windows sockets when building a networked server for XMPP. I believe t
by jconley 10y ago
Back in 2005-2006 we ran into significant issues with the GC and pinned memory related to Windows sockets when building a networked server for XMPP. I believe the GC has improved since then for that scenario, but it was a big surprise when it happened. It was a classic case of a leaky abstraction.
http://blog.jdconley.com/2006/06/how-to-build-scalable-net-server.html http://blog.jdconley.com/2006/06/how-to-build-scalable-net-s...
- zamalek 10y agoI was still in high school when I read that post. Thanks for writing it. Buffer pooling is still incredibly relevant in .Net (as it is in many languages).
- gubbe 10y agoJust for the sake of reference: https://msdn.microsoft.com/en-us/library/system.servicemodel.channels.buffermanager(v=vs.110).aspx https://msdn.microsoft.com/en-us/library/system.servicemodel...
- markdoubleyou 10y agoAlong these same lines, Microsoft.IO.RecyclableMemoryStream is also useful. https://github.com/Microsoft/Microsoft.IO.RecyclableMemoryStream https://github.com/Microsoft/Microsoft.IO.RecyclableMemorySt...