CVI 2013 compiling slow

[Bertrand_ENAC]

Hi,

Is it normal that compiling a project in debug mode takes much more time in CVI 2013 than in CVI 2010?

1'23 minutes versus 0'40 minutes.

When I recompile the project in CVI 2013 without any change to the source code it takes again 1'23 minutes in CVI 2013 versus 5s in CVI 2010.

Is there a setting somewhere which improves compiling speed in CVI 2013?

[Wolfgang]

It depends on the project...

My impression is that compilation of large files is significantly slower, I had reported an example of a factor of more than five, which was later confirmed by NI

[NeluF]

Hello Bertrand_ENAC,

LabWindows/CVI 2013 supports concurrent compilation, which means that you can improve the compile time of large files by splitting them into smaller files. I personally think that each file should have no more than 10k lines of code.

Best regards,

= Nelu F. || National Instruments.

[Bertrand_ENAC]

Hi,

In fact I have large files in my project. One of them has 18000 lines.

I followed your advice and reduce the size of this file to 13000 lines by swaping some code into new files.

I got an imrpovement but it's still disappointing.

With CVI 2010 entering a new empty line to that file gives a compilation time of 12s.

With CVI 2013 entering a new empty line to the file before change (18000 lines) gives a compilation time of 1mn 30s

and with the modified file (13000 lines) it takes 1mn.

So for the time being I will continue to work with CVI 2010 in order to avoid a heart attack.

It's a pitty that a new version is slower than a previous one. I hope this will be imrpoved in the future.

Best regards

[NeluF]

Hello Bertrand_ENAC,

It sounds like your project is compiling really slow. Do you make use of the concurrent compiles option under Build Opions > Build Process Options?

In order to speed up the process, you could disable run-time checking from Build Options > Configuration Options. You could also try to reduce the number of lines per file even further; you should get better results.

Ultimately, you could send us the project to analyse it by uploading it to ftp.natinst.com/incoming. It may be the case that the compiler is slower due to some constructs you're using. Is the memory usage high during compilation?

Best regards,

= Nelu F. || National Instruments.

[NeluF]

Hello Bertrand_ENAC,

I double-checked and the location is ftp://ftp.ni.com/incoming, not ftp.natinst.com.

We look forward to hearing from you,

= Nelu F. || National Instruments.

[Bertrand_ENAC]

Hi,

Number of concurent compiles is: CPUs (4)

When going from "Standart" debugging to "No run-time checking" and adding or removing an empty line to the lagon.c file the compiling time goes from 55s to 14s.

I have uploaded the projetc to your ftp. The name is "Test ELISE-GP CVI 2013"

Thank you for your support.

Bertrand

[NeluF]

Hello Bertrand_ENAC,

Thank you for sending us the project. We will investigate it and get back to you.

Best regards,

= Nelu F. || National Instruments.

[NeluF]

Hello Bertrand_ENAC,

I have reproduced the slowness and opened bug 445424. It will be investigated further, to determine the root cause and possible fix.

Thank you for your feedback,

= Nelu F. || National Instruments.

[Wolfgang]

Hello Nelu,

actually I was hoping that this issue is already tracked...  (bug report 422103)