LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

NXG Style XY Graph Performance Problem

Solved!
Go to solution

 

Hello,

 

I would like to point out a performance issue in the NXG style XY Graph.  I've attached a VI that includes a comparison between the Silver style XY Graph (first tab) and the NXG style XY Graph (second tab).  Notice that the Silver graph seems reasonable (other styles are reasonable also).  You can zoom, autoscale etc. 

 

The NXG style XY Graph performance is abysmal!  My computer grinds to a halt with this same exact dataset.  Why?

 

I'm using LabVIEW 2019 Professional, Windows 10.

 

(I'd really like NI to officially respond to this)

 

Thanks.

DebugGraphPerformance.png

0 Kudos
Message 1 of 7
(3,114 Views)
Solution
Accepted by topic author immercd1

Hi immercd,

 

switch off anti-aliasing in the NXG-style graph to get the same speed as with your Silver-style graph.

(Or the other way around: enable anti-aliasing in the Silver-style graph to make it as slow as the NXG graph…)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 7
(3,052 Views)

Where is the anti-alias setting?

0 Kudos
Message 3 of 7
(3,040 Views)

Aha, I found it!  It's in the Legend, when you right click on a plot.

 

This is definitely the issue.

0 Kudos
Message 4 of 7
(3,019 Views)

Hi immercd,

 

one more comment/suggestion:

Whenever you want to draw a plot with more points then (on screen) pixels are available you should reduce the number of points (aka decimate)…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 5 of 7
(2,967 Views)

Thanks for the reminder about decimation to help with large data plot performance.  I don't think 50K points is enough to warrant it.

 

I just wish NI would actually incorporate decimation into their graphs (or at least have an option to enable it)....this is a staple of any scientific plotting!  It's been in the idea exchange for 10 years!

 

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Decimation-feature-built-into-the-graph-indicators/id...

 

 

0 Kudos
Message 6 of 7
(2,938 Views)

@immercd1 wrote:

Thanks for the reminder about decimation to help with large data plot performance.  I don't think 50K points is enough to warrant it.

 

I just wish NI would actually incorporate decimation into their graphs (or at least have an option to enable it)....this is a staple of any scientific plotting!  It's been in the idea exchange for 10 years!

 

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Decimation-feature-built-into-the-graph-indicators/id...

 

 


According to this, it is incorporated.

 

However, that is not a reason a plot can be slow. Besides anti-aliasing, LabVIEW is a data flow language. The problem with trying to plot millions of points is not because LabVIEW isn't decimating the displayed data, it is because LabVIEW makes multiple copies of the data, one for display, one in the transport buffer, and another one. Making my own decimation didn't speed up the display but it greatly reduced the memory footprint, which in turn sped things up.

 

mcduff

Message 7 of 7
(2,929 Views)