Hi Coastal...
This is just a wild guess.
Is the object configured to run in the Same thread as caller?
We may be seeing some thread swapping going on here.
Done guessing! Please keep us posted.
Ben
a
iIs the object configured to run in the Same thread as
caller?/ip
Yes.
But that doesn't explain (to me) the connection - given that one
execution path is not even running, why is the other penalized?
MORE INFORMATION:
If I make the object RE-ENTRANT, the execution time is back to
normal,
I agree the re-entrant doesn't get us anywhere but it does tell us
something.
When re-entrant we have seperate copies of the VI so one instance ends
up in each execution system and there is no need to swap threads.
I suspect the VI just being loaded is enough for force the thread
swaps.
If you
Sorry for the distraction but,
How about if everything is set for the same thread? This would rule
out the thread swapping theory.
Please let us know what you find.
Curious,
Ben
iHow about if everything is set for the same thread? This would rule
out the thread swapping theory.
/i
--- That's where we came in. I just double checked, and everything is
set to NORMAL - SAME ExeSys AS CALLER (Non re-entrant).
The times are about 11.4 mSec.
If I set the DUMMY priority anywhere
If I set the wasteTime.VI as sub-routine, the undesirable effect
goes away!
I am guessing that on every call of the waste time VI the non-running
VI is checked to see if it wants access to the sub-VI when it is set
for higher priority.
This does not naswer your WHY Q!
I'll watch to see if
I'm chasing a weird timing problem. LabVIEW 7.0 + Windows 2000
I have a VI (called the Object), whose purpose is to store and
retrieve numerical values by name.
The name is hashed, converted to an array index and the values are
read / written to an array slot.
That all works fine.
I have a
MORE INFORMATION:
If I put the Object VI (normal priority) in a brand-new VI, the
tester shows the faster execution time.
If this new VI is set to ABOVE NORMAL priority, the execution time
balloons upward again.
If I raise the TESTER's priority to match (or exceed) the new VI's
priority, it's
