Sign Up
EU Cyber Resilience Act (CRA) — First Deadline September 2026
If you sell LabVIEW-based software and systems in the EU, please be aware that new CRA regulations may require you to implement security vulnerability reporting starting September 11, 2026. The VIPM Team has prepared guides to help you understand how this applies to your software applications and published packages, since it's important you understand these regulatory requirements (click the Learn More link to read these guides). Thank you for your help in keeping security front-and-center within the LabVIEW community.
Learn more
VIPM › Posts › Reduce TMDS File Segmentation by Setting NI_MinimumBufferSize property

suggestion

Reduce TMDS File Segmentation by Setting NI_MinimumBufferSize property

Suggestion shared 2 years, 8 months ago by Steven Dusing
   

Details

Whenever TDMS files are opened, set the TDMS file-level property for NI_MinimumBufferSize to be 10k or something large, since the default is 0. This results in no buffering of the TDMS data in the TDMS cache and can lead to bloated chunks of data getting into the TDMS and index files. I've tested this change locally and it greatly reduces on-disk footprint of the TDMS file sizes. Is there a reason the codebase does not set this property after opening the TDMS files? I think it would be a helpful update if there wasn't a deliberate reason not to.

Comments

Brian Hoover Version 2.2.0.11 now has the minimum buffer size set to 10k in places where the TDMS file is created. I also did some testing and didn't realize the file property meant it was applied to all channels under all groups. That made it much easier to add and reduced the file size on fragmented files a ton. Thanks for the suggestion.
 •  Reply • 1 year

Please sign in to leave a comment.