Is there a way to reset the shared variable engine?

[viScience]

I would like to be able to reset the SVE in a manner that is equivalent to what occurs during a hardware reset.

My motivation for doing so is as follows:

I have an cRIO app with lots of IOV's and NSV's that operate via the SV API and also with plenty of static nodes.  I am finding

that on first run, from the DE, my CPU%=~55%.  On all subsequent runs my CPU%=~65%.  If I do a hardware reset or redeploy one particular NSV library then

my cpu usage will return to ~ 55%.  I have tried isolating the area of code that accounts for this and have found that

the problem centers around my initialization of one library of NSV's where I set its init value via the SV API.  The NSV references

are all closed after writing without error.  So I am wondering if it is possible that the NSV ref's are not actually closing or possibly

the setting of the inital value has some effect on the SVE so that subsequent runs get bogged down.

Anybody have any ideas?

[viScience]

I would like to be able to reset the SVE in a manner that is equivalent to what occurs during a hardware reset.

My motivation for doing so is as follows:

I have an cRIO app with lots of IOV's and NSV's that operate via the SV API and also with plenty of static nodes.  I am finding

that on first run, from the DE, my CPU%=~55%.  On all subsequent runs my CPU%=~65%.  If I do a hardware reset or redeploy one particular NSV library then

my cpu usage will return to ~ 55%.  I have tried isolating the area of code that accounts for this and have found that

the problem centers around my initialization of one library of NSV's where I set its init value via the SV API.  The NSV references

are all closed after writing without error.  So I am wondering if it is possible that the NSV ref's are not actually closing or possibly

the setting of the inital value has some effect on the SVE so that subsequent runs get bogged down.

Anybody have any ideas?

[Tejinder_G.]

Hello,

If you redeploy your library, does that bring your CPU usage back down?  perhaps you can use that as a suitable workaround?  How exactly are you setting the initial value of your shared variables?