minimize the window of LabVIEW 2019 program on windows 11 causes data reading lagging or stopping

[weitong]

LabVIEW 2019-32bit on Windows 11 24H2 64bit.

After minimizing the running LabVIEW program (continuously taking data from instruments) for a while, then taking back the  window of LabVIEW program, I find the data reading are far behind the instruments actually displaying. The program seems stopping/pausing reading the data during the LabVIEW program window being minimized. I test the program on other 2 Windows 11 computers. They all show the same problem. However there is no problem on a win10 computer.

I s there any workaround to solve this problem?

Thanks,

WT 

[GerdW]

Hi weitong,

---

@weitong wrote:

I test the program on other 2 Windows 11 computers. They all show the same problem. However there is no problem on a win10 computer.

I s there any workaround to solve this problem?

---

Use your executable only on Win10 computers.

When you need reliable timings you should think about RT targets…

[Bob_Schor]

Naively, the problem you are describing shouldn't be happening.  But without seeing the code itself, it is difficult to say if there might be something (like in an Event Structure monitoring Front Panel interactions) whether or not there might be something peculiar happening.  Maybe you stumbled upon a new feature, and not a bug.

Can you create a small demo program that exhibits this behavior, save it as its own LabVIEW Project, and then post the entire zipped Project so we can try to help you (and, possibly, NI) figure this out?

Bob Schor

[weitong]

Thanks. The actual program is a little bit complex with lots of dependent VIs. I will make a demo.

The main structure are 3 parallel while loops. Two of them contains event structures. The event structures have 10/100ms timeout events and other events response to front panel operation. 

I also noticed that once the LabVIEW program window minimized, its memory usage dropped a lot from 4% down to 0.6%.

Best,

WT

[GerdW]

Hi Weitong,

---

@weitong wrote:

I also noticed that once the LabVIEW program window minimized, its memory usage dropped a lot from 4% down to 0.6%.

---

When you search for "win11 background apps reduced" the Google AI answers with

Windows 11 background apps can sometimes impact system performance, causing slower response times and increased resource usage. This can manifest as a sluggish feeling, especially when switching between applications or during resource-intensive tasks. To mitigate this, Windows 11 offers features like "Efficiency mode" in Task Manager and allows users to manage background app permissions.

So I guess you need to tweak some Windows preferences/settings…

[weitong]

Is it mean the Win 11 slows down the LabVIEW program running when  LabVIEW program window is minimized?  This is a disaster for a DAQ LabVIEW program.

WT

[GerdW]

Hi Weitong,

---

@weitong wrote:

Is it mean the Win 11 slows down the LabVIEW program running when  LabVIEW program window is minimized?  This is a disaster for a DAQ LabVIEW program.

---

As I already wrote: when you need reliable timings then you should not use Windows OS!

[zou]

It might be worth to experiment the Preferred Execution System under VI Properties => Execution.

Avoid "same as caller" or "user interface".  See if that improves the performance.

[Bob_Schor]

When timing is important, you need to avoid the Windows "clocks" and rely on hardware timing.  Sounds like you might be using the two (two?  as in "more than one"?) Event Loops as part of your timing apparatus, which sounds very problematic.  What hardware are you using?  Anything that could avoid Windows, like a LabVIEW RealTime RIO or PXI system (where the LabVIEW code has the priority, not the OS, Virus scanners, etc.).

Really looking forward to knowing more about your hardware, your "task", a simple task with controls and timing for us to see (and, I hope, improve).

Bob Schor

[weitong]

Thanks.

I tried data acquisition and instrument IO in the Preferred Execution System today, problem is still there.

WT