03-24-2017 03:15 AM
Hi!
I'm working on a project which analyzes projects in VI (when done it'll be available on VIPM). The attached picture show my problematic node.
As can be glanced there's two loops, both parallellized and the other functions are reentrant (and not very advanced), but when running the program I only get 1 working core/thread, most probably due to the Library node not being parallellizable.
The time is from test with lots of Tick counters, it was in the 700-1900ms range for that node, the other were a couple of ms.
Any ideas how i can speed things up?
/Y
03-24-2017 07:13 AM
It doesn't seem i can around it as i hoped, but i'll cache the Library name in a queue for faster future lookups, that should help.
/Y
03-24-2017 07:41 AM
Maybe cache the library path on disk. Does the Library Open method perform any faster? Not sure why it takes so long. Maybe you could also look into not closing these libraries until the end all at once. Maybe there is some kind of deep hierarchy getting loaded and closed causing the long delay.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
03-24-2017 11:42 AM
@Hooovahh wrote:
Maybe cache the library path on disk. Does the Library Open method perform any faster? Not sure why it takes so long. Maybe you could also look into not closing these libraries until the end all at once. Maybe there is some kind of deep hierarchy getting loaded and closed causing the long delay.
That's what i did, i took the VI path and used it as queue name and stored the Library name. It helps, but there are many new lookups ...
With the caching it should only be opened once, so waiting to close won't help much right now.
/Y