Memi.Reflection

Memi asks about using .NET for real-time apps. Naturally, that depends on what kind of application you're writing and what is meant by real-time. Without direct way to access CPU interrupts, deal with direct memory access and assign interrupt priority...

I don't see how plain-vanilla .NET can be considered as any sort of a realtime environment when the GC will suspend all application threads for an indefinite period of time to run finalizers, and the code in finalizers is unbounded.

IMO I'd have to know what definition they are using for realtime before anyone can evaluate if .NET is suitable.

Hey there! I see you liked our talk :)

You can call me on 067-888150.

Basically making the real-time app in .net was based on nothing! .NET had NO market experience was released in the same month I started to work for that company. Since their was no MDX I had to write wrappers and to deal with a LOT of interops. The Application today can grab over 100 frames per second from a video grabber card with 16 inputs. write avi files from those frames (each frame around 300KB) ofcourse display all frames. And a LOT of logic for detections. The performance the application gets have no difference then other equiliant applications in today market. Hardware was then 512MB ram , AMD 2000+ and a 7200 Drive.

One more note though,

When you write a real-time application you consider PERFORMANCE into any step! which mean you HAVE to write caching platform, instance pooling, IO pooling and even thread pooling. Does anyone really think their company have the time and money to do it better then the CLR?

Read my post about it