Slow LabView 2013

[EDGAR_PLATRONICS]

Hi

I have Labview 2013 Professional Dev Sys SP1 ver 13.0.1f2 (32-Bit) and it is slow when I develop any aplication.

For example, if I have a tab control and I change to another tab, it takes about 2 seconds to change tab after I click it.

If i wire a new line, it takes 2 seconds to appear that line in block diagram, and so on.

I have a new computer Dell Optiplex 7010, i7 Processor 3.40Ghz, 64-Bit, 4Gb RAM, WIndows 7 enterprice SP1

If i run Windows task manager it shows 17% CPU usage and 2.14 GB Memory.

If I run for example, excel 2013 it does not seems slow.

Do you have any suggestions ?

Regards

[Yamaeda]

17% sounds like 1 core is spinning crazy. Sometimes mass compile or forced recompile can solve it. There's an old issue with having transparent borders on items if they're overlapped. Does it always happen or with specific VIs?

/Y

[altenbach]

Is that 17% for LabVIEW alone or overall?

The way I understand your post, this is in edit mode. Is it also slow once you run the program?

Do you have front panel indicators (e.g. graphs) containing tons of data.

Yes, check for overlapping objects.

[EDGAR_PLATRONICS]

Hi Yamaeda:

I am not sure about mass compile. You mean rewrite code ? Or create exe file and test?

A this moment I have checked with only one Vi but it is very large. Many sub VIs and code.

Actually it worked correctly in labview 8.5 but i converted to LV 2013.

I will research about transparent borders overlapping.

Hi Altenbach:

17% is overall. 3 cores are high % than others.

The problem is at edit mode and also when I run program.

Yes I have many front panel indicators, but I do not think they have tons of data but I will double check.

When I open my VI in labview it shows 118 MB memory when running and 124MB at edit mode

By the way, last week when by mistake I moved a part of code to some centimeters below, block diagram was frozen and was been updated to new position but line by line until complete full screen. I took about 5 minutes to work normally.

I am using 2 monitors in my PC. One to display LV panel and one for LV code.

[Yamaeda · Accepted solution]

---

@EDGAR_PLATRONICS wrote:

Hi Yamaeda:

I am not sure about mass compile. You mean rewrite code ? Or create exe file and test?

A this moment I have checked with only one Vi but it is very large. Many sub VIs and code.

Actually it worked correctly in labview 8.5 but i converted to LV 2013.

I will research about transparent borders overlapping.

Hi Altenbach:

17% is overall. 3 cores are high % than others.

The problem is at edit mode and also when I run program.

Yes I have many front panel indicators, but I do not think they have tons of data but I will double check.

When I open my VI in labview it shows 118 MB memory when running and 124MB at edit mode

By the way, last week when by mistake I moved a part of code to some centimeters below, block diagram was frozen and was been updated to new position but line by line until complete full screen. I took about 5 minutes to work normally.

I am using 2 monitors in my PC. One to display LV panel and one for LV code.

---

I meant Tools -> Advanced -> Mass compile and recompile your upgraded code. In the same manner a ctrl+run array will force recompile your program. It can help. Else you're down to e.g. using VI analyzer tool to find the culprit, it might be some VI that's corrupted and needs to be moved to a new VI.

/Y

[EDGAR_PLATRONICS]

I created a new very simple VI and it works fast. It shows 54MB memory and overall CPU usage keeps in 17%.

It seems that my problem is related with my specific very large VI but I was working fine in LV8.5

[EDGAR_PLATRONICS]

Thank you Yamaeda. I review my code with this tool.

Regards

[EDGAR_PLATRONICS]

Hi Yamaeda:

When I ran Mass compile, I found some VI's not loaded because were in incorrect path. 

I moved those VI's and now it runs faster.

Tomorrow I will check if any additional performance problem is foud.

Thanks for your help

[EDGAR_PLATRONICS]

I have tested, mass compile fixed my problem.

Thank you