Windows 98 Processor Usage

[Ben]

Please excuse this lame note.

My observations were actually made on a Windows ME machine.

I was under the impresion that Win ME = Win 98.

I am not a IT type so I do not follow these details very closely.

Ben

[KileenC]

We have reproduced this issue here on a Pentium 4, 2 GHz, single CPU, no hyperthreading, 512 MB RAM, running Win2k SP4. Similar behavior is also noted on WinXP.

There is a workaround for the slow saving behavior. Saving via File - Save or CTRL-S is very slow when many VIs are in memory. However, if you edit a VI, close it, and then answer "Save" when prompted, it saves very quickly. You can see this as follows:

1. Open loader.vi, set it to load 1000 copies and open front panels. Run the VI.


2. Hit CTRL-N to create a new VI. Be patient.


3. Select File - Save As, give it a name, and save. Once you click save it takes 10 - 15 seconds on my PC


4. Drop a numeric constant on the dia
   gram. Hit CTRL-S. This took another 15 - 20 seconds on my PC.


5. Drop another numeric constant on the diagram. Close the VI, and when prompted, click Save. The VI saves and closes very quickly.

R&D will continue to investigate the performance behavior. Thanks again!

Kileen C.

[Ben]

I do not think this "workaround" will be very helpful. I have been burned by lost work due to not saving often. I "ctrl-s" almost as often as I switch tools. I would also loose my probes and my State Diagram Editor window.

It may be a very good lead to help figure out what is the root cause.

When we answer the question;
What does LV do different when a VI is saved VS when is closed and saved?

We will know what the issue is.

Keep trying Kileen, you'll get there!

Ben

[Ben]

Hi Kileen,

Are we in the right thread for this discussion?

Ben

[AstroMed_Glen]

My sentiments exactly. If this thread was able to expose a new problem than more power to it. But to reiterate, I was primarily concerned with a processor usage swell that occured after either a LV created exe or session in LV development closed out. This again, was only Win98 (and apparently on WinMe) systems.
I guess it is really a dead issue. Since LV 7.1 Ni stopped supporting Win98, so no future releases would address this issue. Unless there is something that can presently be changed on my Win98 system to remedy this.

[KileenC]

Hi Ben,

You're right, I did accidentally post to the wrong thread as I was in the process of investigating another performance issue with R&D at the same time.

As for this issue, the issue is still being researched and I will post updates as I receive them. I apologize for the confusion.

Kileen C.