My display sensitive application uses memory mapfiles to push bulk data between multiple AppDomains. The fastest mechanism is needed to signal to AD that I get it is that it is new data to be read.
The design looks like this:
1. It should notify the reader ADS
AD2, N ..: Reader of MMF
The readers do not have to know how much data is written because every written The message will be started with a zero zero int and it will be read to zero, do not worry about partially written messages.
(I think) Traditionally, in an advertisement monitor. Waiting / Pulse can be used, I do not think it works on AppDomains.
A MarshalByRefObject Remotting method or event can also be used, but I have to choose something faster
A named EventWaitHandle is about twice as fast as the initial measurement.
Is there something fast?
Note: The received ADS does not need to get every signal until the last signal is left.
Thread references switch costs between 2000 and 10,000 machine chunks on windows if you have one million per second If you want more, then you have to solve the great silicone speed boating. You are already at the very least end of the overhead.
Focus on switching often less and collect more data in one odd one. There is no need to switch to a microsecond.
Comments
Post a Comment