DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Efficient way to use DVR in DQMH modules

Ozfarmboy:

Is the constant allocation/deallocation of memory occurring because DVRs are being constantly created/destroyed going to create a determinism issue?  I am think especially for RT here

 

I had the similar question, What is the memory allocation/deallocation overheads in very frequent DVR create and destroy option(lets say every 50mS) for 24x7 running application?

 

Thank you

 

 

0 Kudos
Message 11 of 18
(1,540 Views)

One additional suggestion for you, in case the data type you stream changes over time, you can typecast the DVR ref into a U32 to make it "embedded-data-type agnostic".

 

TiTou_0-1634719615542.png

 

If you do that, when you typecast back from U32 to DVR ref, place the "create DVR" primitive in a disable struct and the data type out of the disable struct 😉


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 12 of 18
(1,514 Views)

@TiTou wrote:

One additional suggestion for you, in case the data type you stream changes over time, you can typecast the DVR ref into a U32 to make it "embedded-data-type agnostic".


Putting the DVR in a Variant is a safer way to do this, in that you wont crash the program if you cast to the wrong datatype (you'll get an error instead).

Message 13 of 18
(1,511 Views)

...and I was wrong to think that the to-variant + variant-to-data would take longer to execute, it's the same!

I hope LabVIEW will find other ways to crash 😮


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 14 of 18
(1,508 Views)

What is the memory allocation/deallocation overheads in very frequent DVR create and destroy option(lets say every 50mS) for 24x7 running application?

 

Any thoughts on this?

 

Between, Thank you for all your replies, its all great information.

 

Thank you

0 Kudos
Message 15 of 18
(1,476 Views)

@AdarshaPakala wrote:

What is the memory allocation/deallocation overheads in very frequent DVR create and destroy option(lets say every 50mS) for 24x7 running application?

 

Any thoughts on this?

 


My thought is to wonder why you haven't just measured DVR overhead with a simple test VI.  Make and destroy 10,000 DVRs per second and run that overnight.

0 Kudos
Message 16 of 18
(1,469 Views)

 

I already did that. I was wondering, I would get more information, if some one already had experienced with bigger application in this scenarios. The behaviour could be different in bigger applications when there is a lot of thread switching, thermal managing/throttling,  large memory management and etc are happening.

0 Kudos
Message 17 of 18
(1,464 Views)

So you are asking if anyone with experience using DVRs in this way has had any problems.  That is a better question.

0 Kudos
Message 18 of 18
(1,457 Views)