LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Slow Loop Rate / Low CPU Utilization

Solved!
Go to solution

Thank you all again for all the great feedback! I got a lot out of this thread - looking forward to fixing this.

0 Kudos
Message 11 of 13
(238 Views)

Quick update:

I ended essentially replacing all queues (incorrectly implemented) with notifiers. All the consumers are displays, so they can be lossy.

For lossless data collection from the two sources, I created queues for these.

While doing this, I discovered the source of the slow loop rate: it was a property node (thanks BertMcMahan).

0 Kudos
Message 12 of 13
(212 Views)

@wttester wrote:

 

1. [snip] However, what is not clear to me is this: If I have multiple consumers of the queue (i.e. other displays), then which consumer does the de-queueing to guarantee all consumers get data before it is dequeued?

Many to one = queue. One to many = Event. You could go with separate queues also, it depends a little on which information is sent.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 13 of 13
(191 Views)