RE: Detecting data lost from a subscriber

["Dalesio, Leo" <dalesio@bnl.gov>]

Perhaps I was not clear --

What if the client is trying to do something very slow with the monitors and is NOT consuming them at the same rate that the server is creating them.

This is the reason that rsrv for the EPICS database needs to start overwriting the last thing on the queue. It does not let the queue get over some specified size. If you just keep allocating memory and the client is not consuming the data fast enough, you use up your memory and eventually crash the system. At least I would expect this. It is likely a good idea to put something in to prevent this.

Bob

-----Original Message-----
From: Bruno Coudoin [mailto:bruno.coudoin@eads.com]
Sent: Thu 7/9/2009 3:46 AM
To: Dalesio, Leo
Cc: Andrew Johnson; tech-talk@aps.anl.gov; Ralph Lange
Subject: RE: Detecting data lost from a subscriber
 

Le mercredi 08 juillet 2009 à 13:13 -0400, Dalesio, Leo a écrit :
> What do you do if the client is not consuming - but the server
>  continues to create arrays?

The same as for scalars, once they are sent or discarded the gdd will be
unreferenced by the CAS, but for arrays their gddDestructor will free
them.

Bruno.