The NetPerfMonservice.exe is single-threaded.
Are there any plans to make Orion Multi-Threaded?
Yes, but it's not as urgent as some other features such as web-based administration, enhanced and easier-to-use custom MIB pollers, automatic alert suppression based on topology, AD integration, etc. Those are all issues that I hear about frequently. They expand Orion in significant ways. Multi-threading would be cool and when we do it, it will improve performance, but it's more incremental than these other features. If I had a magic wand (that I could only use on Orion--an important distinction, because otherwise I can think of way better things to do with a magic wand), I would add all that and more to Orion. However, while I remain wandless, we have to be careful about which featureswe add to Orion. If we try to change too much all at once, we can reduce stability or otherwise mess it up. So we're adding feature aggressively but not recklessly. 2008 is going to be a great year for Orion releases, so stay tuned.
Just to cloud up the issue:
NetPerfmonService.exe is single threaded only in how it coordinates the information collected. Information is collected in an asynchronous multithreaded manner. All other Orion services are fully multithreaded.
In a four core system if I see the Netperfmonservice.EXE using 25 % of system CPU recourses I could say that performance is being impacted , right?
Correct, due to some COM usage NetPerfMonService.exe won't span more than one physical processor so there is certainly room for performance enhancement. However, the multiple collection threads that NetPerfMonService.exe has allows the processor it has access to to continue processing data while it is waiting on devices to report back to it.
Hate to bring up an old topic, but I cant seem to find an answer anywhere. Is Orion Multithreaded yet?
The vast majority of Orion is already multi-threaded. The NPM service is still single-threaded, but we've offloaded quite a bit of the work to other services that are multi-threaded.
