LabVIEW 8 very slow to edit large VI

[DanyAllard]

Hi,

I have upgraded a software to LabVIEW 8 last week and I found that LV8 is very slow to edit Block Diagram of a large VI. (2Mb VI's).

When i create a wire it take 3 sec to apper, it's the same thing by dropping a VI or a structure. This behaviour makes LV8 unworkable.

This behaviour is not present in LabVIEW7.1 ... For example a VI file in LabVIEW 7.1 of 7Mb is very fast to edit, and when I convert the VI to LabVIEW 8 the file is reduced to 2Mb and very slow to edit. I imagine that the compiler was optimised to get smaller VI files, but that create a delay while editing the VI's by compiling each time that  something new is dropped to the diagram.

Is there a way to optimize the speed for editing a Large VI's?

I don’t want to split those Big VI to smaller parts... I don’t have the time and the budget to do so.

Now I am thinking to downgrade to LV7.1 to be more productive... 

Thanks

Dany

[altenbach]

I think the file size on disk is irrelevant once the VI is in memory.

Can you tell us a bit more about your VI. Do you have a huge number of property nodes?

[xseadog]

Hi
what also springs to mind :
PC configuration, hard disk space, Ram etc.
I believe the recommendation is 512MB for Labview 8.

xseadog

[DanyAllard]

HI,

I have no problem with my PC : 2.5 GHz  1.2G of RAM 12G of available space on disk... we got the same behaviour on 4 differant PCs for Big VI...

The big VI's that I talk are big state machine driven by queue. There is no special stuf in it...

My concern is, if it's work in 7.1, it should work in LV 8. What as been change in LV 8 that generate this delay while editing my VI?

Is there a special INI key that I can put in my Labview.ini that optimize the compile time of minor change in editing?

Is there a background service that can be disabled to crank up the compile speed?

Some one at NI can respond to these questions?

My immediat solution is to downgrade to LV7.1 and wait for the next release of LV... or Patch...

Thank for your help

Dany

[Ben]

I can not offer any suggestions but I can ask questions.

If you go to the diagram and copy everything and paste it into a new VI, does the new VI edit faster? (attribrution: This wild guess was inspired by a posting from C. Altenbach in a private forum).

Ben

[EdDickens]

I recently had this same problem and traced it down to a Type-Defed control. It was a simple emun used to control a state machine.

Saving the control with a new name fixed the problem.

Ed

[DanyAllard]

Thanks you all for the reply

I open a service request with NI

I will submit my VI's for investigation

Thanks

Dany

[Ben]

Hi Dany,

If you get the oppertunity, could you let us know what you find out in the end?

It may help us help others in the future.

Ben

[DanyAllard]

No problem Ben

Dany

[DanyAllard]

There is the last reply from NI i got to this issue

<QUOTE>

Hey Dany,
Just wanted to check in with you again before the service request closes up
to see if you have any other questions. We did find out that the inner case
structure seems to be causing the problem. You haven't done anything wrong
nor can you really do anything to improve your code. There just seems to be
a bug and R&D is going to look into the problem. Let me know if you have
further questions. Thanks!

</QUOTE>

It's a bug...

Dany