I recently installed labview on a new Windows 8 Laptop and four NI Labview Services are consuming a high amount of processor even while Labview is not running.
lkads - NI PSP Service Locator
nidmsrv - NI Domain Service
lktsv - NI Time Syncrhonization
NI Variable Engine
Each one is using 16%-17% (combined total of 66%) processor and this is on an i7. Has anyone else run into this and found a way to reduce the processor utilization?
Being the weekend, I can’t really talk to anyone in that group, but I don’t know that you need any of those services running. I’ve seen them have high CPU usage at times, but I couldn’t find anything on the support site specific to win8.
So I’d disable the lookout and variable services one at a time and see if there is some sort of odd interaction between them. The network variables aren’t used by the default code, but I have seen some teams use them. If that is the case, it would be the one that I’d leave on.
Greg McKaskle
I’d be curious to know to what extent this is affecting windoze scheduling jitter.
If you go here and download and run the Win32 Process Scheduling demo app, it will display scheduling jitter in a command window.