From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

DQMH Consortium Toolkits Feature Requests

cancel
Showing results for 
Search instead for 
Did you mean: 
Olivier-JOURDAN

Improve Module validator performances

I'm triggering module validation with CI. On a large project (40+ modules), the validation takes 20+ minutes to execute.

 

I'm wondering if there are ways to reduce this execution time.


Olivier Jourdan

Wovalab founder | DQMH Consortium board member | LinkedIn |

Stop writing your LabVIEW code documentation, use Antidoc!
3 Comments
joerg.hampel
Active Participant

...and/or supply a hook into what's happening, so we can at least update the UI or CLI, as described here:

 

https://forums.ni.com/t5/DQMH-Feature-Requests/Expose-events-for-Headless-Validation/idi-p/4068427




DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (The Future of Team-Based LabVIEW Development)


Olivier-JOURDAN
Active Participant
Status changed to: Development Started
 

Olivier Jourdan

Wovalab founder | DQMH Consortium board member | LinkedIn |

Stop writing your LabVIEW code documentation, use Antidoc!
Darren
Proven Zealot

There is definitely room for improvement in the validation tool in terms of performance. Lots of the individual validation tests do their own parsing that could probably be done once by the engine and passed in to the tests. For example, if the engine opened references to all ProjectItems and VIs that live in the module library, I imagine each validation test would run much faster.