Would using a MemoryMappedFile for IPC across AppDomains be faster than WCF/named pipes?

Posted by Morten Mertner on Stack Overflow See other posts from Stack Overflow or by Morten Mertner
Published on 2010-03-19T18:10:37Z Indexed on 2010/03/19 18:11 UTC
Read the original article Hit count: 227

Filed under:
|
|
|

Context: I am loading and executing untrusted code in a separate AppDomain and am currently communicating between the two using WCF (using named pipes as the underlying transport). I am exchanging relatively simple object graphs using a reasonably coarse-grained API, but would like to use a more fine-grained API if it does not cost me performance-wise.

I've noticed that 4.0 adds a MemoryMappedFile class (which doesn't need a physical file, so could be entirely memory based). What kind of performance gains could I expect to see (if any) by using this new class?

I know that it would take some "infrastructure code" to get the request/response behavior of WCF, but for now I'm only interested in the performance difference.

© Stack Overflow or respective owner

Related posts about .net-4.0

Related posts about Performance