Jump to content

LV2020 Slow To Create SubVI


Recommended Posts

I have been using LV2020 for a bit recently and have noticed that it is extremely slow to create a SubVI from a selection. This is the kind of thing I do quite often and I am used to it happening mostly instantaneously. In LV2020 this operation now causes the LabVIEW process to ramp up CPU usage and my laptop fans start to spin noisily and about 30s later I get my SubVI.

Anyone else seen this?

Link to comment

Sounds like the compiler is busy figuring things out.
Just tested it on the QMH template and it is as fast as always (1-2 seconds). That said, the template is not very complex. Do you get better results with a simple project like that?

Link to comment
24 minutes ago, LogMAN said:

Sounds like the compiler is busy figuring things out.
Just tested it on the QMH template and it is as fast as always (1-2 seconds). That said, the template is not very complex. Do you get better results with a simple project like that?

Just did a quick test. Started LV2020, did not start or open a project just created a new VI. Did some simple stuff and then created a Sub VI from some of the diagram contents. Just doing this took nearly 30s šŸ˜ž

Link to comment
2 hours ago, Darren said:

Try mass compiling theĀ [LabVIEW 2020]\resourceĀ folder? LabVIEW should install the compiled cache for this already, but maybe something got messed up?

Nice tip Darren, thanks that did seem to work.

Got heaps of errors when mass compiling though! Will do it again sometime and log the results to disk.

Link to comment

I'm glad that helped. But that also tells us that your installed compiled cache for core LabVIEW was either missing or somehow broken. You may want to consider repairing your LabVIEW 2020 install, or doing a mass compile of the whole LabVIEW folder, to make sure your core compiled object cache is up to date.

Link to comment
2 minutes ago, Darren said:

I'm glad that helped. But that also tells us that your installed compiled cache for core LabVIEW was either missing or somehow broken. You may want to consider repairing your LabVIEW 2020 install, or doing a mass compile of the whole LabVIEW folder, to make sure your core compiled object cache is up to date.

Cool, I will do the full mass compile this evening.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.