Using network variables on a single computer with multiple programs

[rlf130]

Hello all.

I am a first time poster, long time reader of the forums/user of NI software.

Ok, so I'll cut to the chase.  I am currently using Network Variables to send data between multiple computers (5 currently).  I recently completed an upgrade/migration cycle to combine programs and consolidate computers down from 7 to five, and update all of them from using datasocket to network variables and all of them performed very well without many bugs or program gremlins.  In this update, instead of having every program with a dedicated computer, some of our less intensive programs have been consolidated onto less computers.  Now, on a couple of these computers where it is running two programs both hooked up to the network variables, I have noticed a drastic decrease in response time to the network variables (counters that used to update multiple times per second now update every 10 seconds etc).

So my basic question is the following: 

Does network variables not work well when multiple programs on the same computer are trying to access it?

Do I currently have to have a seperate computer for each program or combine programs into a single monolithic program?

Some more addt'l data:

Three of the computers are running XP.

Two are running Vista Enterprise.

All are running Symantec Endpoint Protection v 11.0.

The network variable manager itself runs off of a server running Server 2003 Enterprise.

All programs written in Visual Basic 2005 or 2008.

I would appreciate any assistance in this matter.

Thanks for your time,

[Steve_InMA]

At times I've had multiple application (3) running on the same computer and connecting to the same engine.  I have not noticed any decrease in responsiveness.  The applications I'm running all subscribe to NVs and so receive events on NV change.  I found this to be a bit more responsive than polling (aka reading) the NVs.

[penewman]

these counters are textboxes?

how many counters are displayed by the program?

each counter display is "tied" to one network variable?

and that network variable is an array datatype? or not an array?

are the network variables hosted on the same computer as the counter display?

or do you have to go across a network to see the network variables? 

rather than use the deprecated datasocket, have you considered upgrading to 

measurement studio's network variable class?

i have three computers

one computer hosts the network variable

and the other two computers point at it (over the network)

and then display the data in a bunch of waveform controls

if i try to run two instances of the waveform control app on 

one computer the CPU pegs.....

how is your CPU doing when the slow down occurs?