Lookout slow to save file

[Beardsell]

We are trying to migrate out plants 3.8 to 6.2.  Out 3.8 project saves in <10 sec to the local drive but the same project imported into 6.2 takes 20+ seconds.  Since our PLC communications are down during this time we have to shutdown in our operation.  Looking at the Shared Variable Engine we have appx 12,000 variables located in one process and I assume it has something to do with the extended save times.  I was wondering if I create folders or break up our project into different processes will this solve the problem.

[Ryan.S]

Shared Variable Engine is in LabVIEW. How do you use it with Lookout?

Do you mean that Lookout takes 20 seconds to save the process files?

[Beardsell]

Maybe I should have used the term Logos.  We use SVE/Logos interchangeable in conversation from a non technical level.  The 20+ second save is in regards to Lookout.

[Ryan.S]

So you have 12000 shared variables and use Lookout to read or write them.

Is it the process file's save from File menu, or the periodical state file's saving?

[Beardsell]

We have 1 process file and all objects are in the root folder of that process. If I use the Distributed System Manager I can see there are appx 12,000 registered variables under that process and I am questioning the quantity of variables under one process. The slow save times happen when saving the process file from the File menu. I am not sure if the two are linked but I am looking for some insurance before I start splitting up the process file.

[Ryan.S]

I'm sorry I don't have idea if the long save time is related to the number of variables. But I'm a little bit confused. Are the 12000 variables the shared variables from LabVIEW or the variables in Lookout process?

If it's okay for you, you can upload your process to ftp://ftp.ni.com/incoming. I will check it out and do some tests for you.