Why gauges in measurement studio takes so much system resources?

[taras_33]

I'm using 10 analog inputs for data acquisition. (NI 6212) To see them I use 10 gauges, in this case the CPU is 100%. If I use NumericEdit instead of gauges that everything is normal, the CPU 8%. What's wrong? Technical information: Measurement studio 8.6 for VS2008. Continue acquisition, rate 1000, samples 100. Thanks

[Swathi B]

Hi taras_33,

Welcome to the NI Discussion Forums! When creating a Measurement Studio NI DAQ Windows Application (with Visual C# and VB.NET) for continuous acquisition, the default data display in the Generate DAQ UI Wizard is a WaveformGraph. Could you help clarify how you are displaying continuously acquired data with a Gauge or a NumericEdit? Thanks!

[taras_33]

In the attachment is a project created in VS2008 (MS8.6), I modified the example from the examples folder. Unzip, run and check system resources. Thanks for your reply

[Swathi B]

Hi taras_33,

Thanks for the clarification. I tried running your code on Visual Studio 2008 with Measurement Studio 8.6, and I noticed an increase in CPU usage by about 10-15%, so not nearly as drastic as in your case. I was using a Windows 7 machine with 3.00 GHz processor speed. What are the specifications on your machine?

[taras_33]

The question is not in the power of a computer. I deliberately use the weak computer (Pentium 3,  800MHz, Xp) for "best effect". The question is why such an algorithm for acquisition data, written in LabVIEW takes much less system resources. See attachment

[Swathi B]

Hi taras_33,

As we had discussed, you are going to notice an increase in system resource usage when implementing Gauges as opposed to NumericEdit indicators in Measurement Studio because Gauges are more graphically-intensive. However, because your application that uses Measurement Studio uses the .NET Framework while your LabVIEW application uses the LabVIEW Run-Time Engine, we can't compare the two and expect to see similarities. In fact, when I executed the LabVIEW 2009 code that I re-created from your screenshot, my CPU usage was higher than the other two instances.

[Swathi B]

taras_33,

I also looked at the Measurement Studio 8.6 for Visual Studio 2008 Readme for installation requirements, and it does appear that the minimum processor requirement is an Intel Pentium III class processor, 1 GHz or higher. With Measurement Studio installation, you can access the Readme file from Start » Programs » National Instruments » Measurement Studio » Readme.

I hope this helps!