LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Global "pseudo-WORM" or preview Notifier?

Access to a functional global is your biggest source of jitter?   But your "heavy load" access rates are in the order of ~5 client accesses per 50 msec?   That doesn't actually sound very demanding.   Is the code structured to cause client accesses to be syncronized rather than asynchronous?  Are you sure the jitter is due to access and blocking effects rather than variable time spent inside the func global (or even elsewhere)?

 

Well, regardless, you may as well make the fairly simple switch to a standard global variable so you can compare.

 

-Kevin P

ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
0 Kudos
Message 11 of 12
(372 Views)

Q,

 

How much data is involved? If it is small, spawn a copy for each client process.  Then the only delay you have is at launch time and you will never have blocking.

 

Lynn

0 Kudos
Message 12 of 12
(356 Views)