Fast interprocess communication of large data between c# .net applications on same computer.:

Question

0.00/5 (No votes)

See more:

Hello Everyone,

I am wondering if the solution I am currently using for a project is the best approach.

Here is a short description of the project:

Two applications (C#) one is a server and the second a client will send and receive a queue of float array data. This data will be in real time drawn on a chart on the client side.

I am currently using message queue but I wonder if I will not be obliged to cut the message in peaces if the float array is exceeded the message limit.

What is you view on that ?

What would be your best candidate between:

• Message Queue
• Named Pipes (directly)
• Memory mapped files
• WCF on Named Pipes or MSMQ

Thank you in advance.
Best regards.
MiQi.

Posted 5-Mar-14 3:04am

SuperMiQi

Add a Solution

Comments

dan!sh 5-Mar-14 9:09am

Both server and client applications run on same computer?

SuperMiQi 5-Mar-14 9:11am

yes on the same computer

2 solutions

Solution 2

No need to use named pipes directly if all partners are working on the CLR platform. There are channels called "IPC" in both "classical" remoting and WCF (which can be self-hosted, in a simple case). These channels are actually based on named pipes. However, there is nothing wrong with using TCP, even on the same computer. Note that originally sockets were created not as a network tool, but just for IPC in the same machine.

—SA

Posted 5-Mar-14 6:34am

Sergey Alexandrovich Kryukov

Updated 5-Mar-14 6:36am

v2

Comments

dan!sh 5-Mar-14 13:04pm

This guy want real time solution for his problem. Under no circumstances anyone would say use WCF if he understand how much reflection goes under the hood with it. It is over designed. Not suitable here.

Sergey Alexandrovich Kryukov 5-Mar-14 13:24pm

There is no such thing as "realtime" with Windows and nearly all other platforms where CLR is supported.
At to your "unsuitable", it's just wrong. Do you think lower level of OS pipe API will give you more performance? Think again.
—SA

dan!sh 5-Mar-14 13:32pm

Read my reply. I said real time like. Hell, if you really want to get into real time argument, I would say scrap whatever you have and use C. Even better, assembly language.

Yes. It will be far better than WCF.

Sergey Alexandrovich Kryukov 5-Mar-14 13:59pm

Not convincing. And the question is about .NET.
—SA

dan!sh 5-Mar-14 13:10pm

And as far as sockets go, anonymous pipes would beat them when it comes to speed.

Sergey Alexandrovich Kryukov 5-Mar-14 13:25pm

Maybe, but I'm not sure. Did you actually time it? I did not.
—SA

dan!sh 5-Mar-14 13:35pm

I did not state this through my research. MSDN states in opening line of one of the pages (which basically was related to IPC) I read a long time back that: "Anonymous pipes have least overhead.". Or something like that. They said it is light weight and hence quicker in an managed environment.

Sergey Alexandrovich Kryukov 5-Mar-14 14:02pm

That is possible, but what would be performance difference? Would not this difference be absorbed by the application-level code of the developers, where the performance could be lost?
I never trust such Microsoft statements, as I had a chance to check things up; and sometimes results confirmed Microsoft statements, sometime not. There is a number of just not quite accurate claims.
—SA

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

*dan!sh* · Accepted Answer · 2014-03-05T03:16:00

Solution 1

Since you are doing real time like processes, make use of pipes. This[^] MSDN page provides decent information to start off.

Posted 5-Mar-14 3:16am

dan!sh

Updated 5-Mar-14 3:17am

v2

Comments

Sergey Alexandrovich Kryukov 5-Mar-14 12:36pm

I voted 4. This is possible, but using named pipes directly would break platform compatibility of the product. It's better to use pipes as IPC channel with remoting or WCF. Please see my answer.
—SA