LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Lag Issues When Stopping LabVIEW Code Execution

Solved!
Go to solution

A HDD can have 180MB/s sequential and 1MB/s random write speed, but this shouldn't be a random write unless OP is writing 1 channel to each file and that equates to "random" write.

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

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 11 of 12
(77 Views)

@Yamaeda wrote:

A HDD can have 180MB/s sequential and 1MB/s random write speed, but this shouldn't be a random write unless OP is writing 1 channel to each file and that equates to "random" write.


I tent to take these listed specs with a grain of salt. I am just reading what it says on the picture. Since we still have no idea what the OP is actually doing we are completely in the dark. It was mentioned that 120 files are saved, so there will be 120 different sequential writes plus all the overhead of opening and closing each. There could be other bottlenecks, for example if the disk uses bitlocker software encryption (now the default for windows 11 pro).

 

Story: Many years ago, IT installed software encryption (Symantec, if I remember right?) on a laptop, even though the SSD had built-in hardware encryption. The effect was that it took well over a minute to wake the computer from hibernation because the 16GB ram image had to be decrypted using the CPU. After undoing that mistake, it again woke up in seconds.

0 Kudos
Message 12 of 12
(52 Views)