Hi Speed Challange (or better High Speed challenge?),
in order to avoid some disappointments, you should first consider if the communication is the 'bottle neck' of your app. I do not know if your assumption about this is proven valid. You may want using NI-Spy or any other tool to check the real transfer rate of your app. You may as well estimate the data transfer rate between your device and your application.
There are at least two other possibel reasons for a slow response:
1. A high CPU load due to lots of calculations.
2. Non-optimal programming (one single thread polling UI AND ports AND doing calculations.
To try to answer your other Qs:
> ... "high performance" cards don't have isolation as an option. Why ...
Isolation uses some non-electrical transfer bridges, either optocouplers or transverters. Those have limited bandwidth and start becoming really expensive with higher bandwidth. 2Mbits is quite a high transfer rate for this.
> Is "Real-Time" what I need?
Depends. Real time means, that your app must react within a specified time frame under _any_ circumstances. This can not be proven using simple OS like Windows, because other apps can block or crash the OS. If your real-time needs are some seconds _and_ you have a kind of watchdog, than Win may as well be enough.
So to decide if you need a real-time solution does mean to decide what 'real-time' does mean for your app. You stated:
> ... need to get feedback from instruments quickly, but not at spectrum analyzer speeds ...
That's too vague.
You may want to ask the author of your current app for some more details about his program design and for the sources. You may need them when exchanging HW.
Sorry for this long winded and somehow vague answer, but your Q was too unspecific.
Greetimngs from Germany!
--
Uwe