Databases
StackOverflow2013
Postsdbo
POWhen messages get bigger, IpcChannel Remoting gets slower
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhen messages get bigger, IpcChannel Remoting gets slower
    primarykey
    data
    text
    <p>I'm evaluating various interprocess communication methods for a couple of <strong>.NET 2.0</strong> processes residing <strong>on the same machine</strong>. Naturally, .Net Remoting is a candidate, and theoretically the fastest configuration should be IpcChannel (named pipes) + BinaryFormatter.</p> <p>My benchmarks really do show that Remoting over IpcChannel could mostly be faster than TcpChannel, but IpcChannel shows a steep drop in throughput as messages get bigger (around 30 MB):</p> <pre> Message Size 30 MB 3 MB 300 KB 3 KB Remoting / TCP 120 MB/s 115.4 MB/s 109.5 MB/s 13.7 MB/s Remoting / IPC 55 MB/s 223.3 MB/s 218.5 MB/s 20.3 MB/s </pre> <p>Does anyone have any idea why, or any idea how to optimize performance of either channel? I do need to pass 30 MB BLOBs around, and would like to avoid having to deal with shared memory / memory mapped files. Also, I can't afford writing these to disk (much slower).</p> <hr> <p>The following method was used for the benchmarks (called repeatedly, measured total time, divided total <em>payload</em> size by total time).</p> <pre><code>private byte[] _bytes = null; public byte[] HelloWorld(long size) { if (_bytes == null || _bytes.Length != size) _bytes = new byte[size]; return _bytes; } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USYodan Tauber
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhen messages get bigger, IpcChannel Remoting gets slower
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhen messages get bigger, IpcChannel Remoting gets slower
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhen messages get bigger, IpcChannel Remoting gets slower
      1. USPavel Radzivilovsky
      1. VTBountyStart
    1. COJust a thought, have you confirmed that with the larger payloads the messages are NOT getting cached to disk somewhere? Here's the reason I ask- IIS 7 automatically spools large requests to disk to avoid consuming too much RAM...I'm wondering if either .Net or Windows implements a similar behavior and when the message size increases, hidden disk i/o occurs. If not disk i/o, my next guess would be the message chunk size.
      singulars
      1. POWhen messages get bigger, IpcChannel Remoting gets slower
      1. USTim Medora
    2. CO@Tim: I haven't. Assuming that I do find out that it has to do with hidden disk i/o, is there anything I can actually do about it? e.g. reconfigure Remoting or IpcChannel to behave differently?
      singulars
      1. POWhen messages get bigger, IpcChannel Remoting gets slower
      1. USYodan Tauber
    3. CO@Yodan - I don't know how you would reduce hidden disk caching but it might have something to do with how much RAM is allocated to the process(es) in question. Have you looked at resource consumption on the machine when sending large messages repeatedly? Even with very large files (I've tried with 500MB+) pure stream manipulation (like transferring data from one process to another) results in very little memory consumption and no disk i/o. Therefore, if you see RAM/disk spikes (especially if you see differences between TCP and IPC) it may give you an indication of what is going on.
      singulars
      1. POWhen messages get bigger, IpcChannel Remoting gets slower
      1. USTim Medora
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload