wait ms timer value

[dg_lbe]

Will locate book.

[Ben]

---

@dg_lbe wrote:
Will locate book.

---

Good becuase...

---

The reason for the While loop instead of the FOR loop was I read that using a while loop the CPU memory allocation desision is made once where as the FOR loop it occurs every time.  So I would then say this means its faster.  IS THIS NOT TRUE??????? 

---

my reply is "NOT TRUE"!

THere was a period of time between LV 6i and somewhere around LV 2009 when the exact inverse was true (For loop preallocates the output buffer once before it stats to execute) but the while loop was never faster in any test I ever did or anything I may have read.

Take care,

Ben

[altenbach]

---

@Ben wrote:
THere was a period of time between LV 6i and somewhere around LV 2009 when the exact inverse was true (For loop preallocates the output buffer once before it stats to execute) but the while loop was never faster in any test I ever did or anything I may have read.

---

Ben, you are confusing me. Are you saying that something related to this question changed in LV 2010? In what way?

I would say that the FOR loop preallocates autoindexing outputs in any modern LabVIEW version.

[Ben]

---

@altenbach wrote:

---

@Ben wrote:
THere was a period of time between LV 6i and somewhere around LV 2009 when the exact inverse was true (For loop preallocates the output buffer once before it stats to execute) but the while loop was never faster in any test I ever did or anything I may have read.

---

Ben, you are confusing me. Are you saying that something related to this question changed in LV 2010? In what way?

I would say that the FOR loop preallocates autoindexing outputs in any modern LabVIEW version.

---

Well confusing people is the last thing I want to do.

I agree with your above staement as is.

If I run across something definative, I'll share it.

Take care,

Ben

[rolfk]

---

@altenbach wrote:

I would say that the FOR loop preallocates autoindexing outputs in any modern LabVIEW version.

---

This has been the well known behaviour of any LabVIEW version since at least 3.0 and most likely also in 2.x.

[dg_lbe]

Sorry for the delayed response.  Attached is a sample of a deployed application that results in having a normal loop time of 35ms.  When the target laptop comes out of standby the time increases to 70ms.  The cure is to close the application and reload or have the power option set to never go into standby.  

Thanks.........  

[dg_lbe]

Sorry for the delayed response.  Attached is a sample of a deployed application that results in having a normal loop time of 35ms.  When the target laptop comes out of standby the time increases to 70ms.  The cure is to close the application and reload or have the power option set to never go into standby.  

Thanks.........