06-04-2007 01:10 PM
06-05-2007 07:45 PM
06-06-2007 02:07 AM
06-06-2007 06:30 AM
Thanks guys. A few things I have since discovered. First, scratch the problem with only executables. I installed the development version on one of our core duo machines, and saw the same slowing behavior. Since we need to deploy on core duo, I changed the timed loops to while loops, and it runs ok now. Most of the time the execute at their set rate - between 50ms - 250ms. A slow down can happen at any time, even if I haven't touched the machine for minutes.
JB - you mention changing priorities. Most loops have a variable priority depending on the state of the front panel vi in the timed loop (50 if closed, 190 if open, 210 if open & in front). The number is always sent to the "priority" input on the right side. Most of the time the priority doesn't change, and even if it does, only one does at a time (assuming the user only does one window action - open, close, pull a different one to the front - per 250ms). If I read you right, you are saying that I sould only wire this when it is to change, which I assume means wire a "-1" when it is not to change? If that is what you are saying, I'll have to give it a try.
Also is their anyway to turn off hyperthreading - or remove the duoness of the core duo? I didn't see anything obvious (but I often miss stuff like that).
06-06-2007 07:54 AM