It isn't clear to me what the difference is between "we tested and it on simulation mode and it worked very well" and "real machine online testing at industry online production envrionment":
- What are the differences between the simulation machine and the production machine?
- Can you simulate these differences?
- When you say that you "tested it on simulation mode", did you do performance/load testing (generating, in your simulation, as many events per second as you expect on the real machine)?
- Do you allow any extra margin for safety (e.g., I might feel comfortable if my testing shows that my software needs only 10% of the machine's CPU capacity ... because then even if if it needs 10 times more than that in real life, that's still enough)?
- The end-user/customer will eventually do acceptance testing on the real machine. Can you work with them, to get you access to the real machine?
We worry about if there is some Com Event Sending from CppApp to CsApp delay
Well, COM is faster when it's used in-process instead of inter-process or out-of-process: when the COM object is a DLL loaded into the same process as whatever is using it.
Is there any resource which i could research about Com Event performance for industry application?
I don't know; for what it's worth, the article Events vs. Callbacks says,
Performance Issues
When performance is at stake, it will
usually be worthwhile to do the extra
work required to create custom
callback interfaces. By employing
early binding in the callback
interface connection code, significant
improvements can be made in
high-volume or in-process components.
By design, event interfaces are not
vtable bound and are, therefore,
slower in most scenarios than
comparable early-bound callback
interfaces.
Of course, in any performance issue,
the only way to gauge your own needs
is to experiment, benchmark, and test.
Try out the various permutations
yourself and do the math. If you
really care about getting the absolute
last spurt of speed, then doing the
tests is the only way to prove what
works, no matter what promises are
made.
Other articles in that section of MSDN are also relevent to performance, for example Understanding and Using COM Threading Models