Experimental Physics and
Industrial Control System

"Jeff Hill" <[email protected]> · Fri, 6 Jun 1997 10:03:45 -0600

William,

>   I have a stringin that can be processed several times rapidly in
> succession with a different .VAL field each time. I get a monitor for
> each time it is processed. However, the monitored values are mostly the
> same.
> 
>   For example (pvload is a tool that processes a list of channel assign-
> ments; "group" uses ezcaBeginGroup()/ezcaEndGroup()):
> 
> % pvload
> group {
>     string k0:ao:sc:state = "a";
>     string k0:ao:sc:state = "b";
>     string k0:ao:sc:state = "c";
>     string k0:ao:sc:state = "d";
>     string k0:ao:sc:state = "e";
>     string k0:ao:sc:state = "f";
> }
> 
> camonitor k0:ao:sc:state
>  k0:ao:sc:state                 06/04/97 12:16:59.400 a 
>  k0:ao:sc:state                 06/04/97 12:16:59.410 f 
>  k0:ao:sc:state                 06/04/97 12:16:59.410 f 
>  k0:ao:sc:state                 06/04/97 12:16:59.410 f 
>  k0:ao:sc:state                 06/04/97 12:16:59.410 f 
>  k0:ao:sc:state                 06/04/97 12:16:59.410 f 
> ^C
> 
> 

Due to concerns about excessive memory consumption in 
the CA server's monitor queue, we do not queue up
the intermediate values for monitors on fields whose
native type in the database is DBR_STRING. This also
applies to fields of more than one element (arrays).
We will however always send an update for the final value
so that clients will remain current.

>   Is there anything I can do to prevent this behavior? 

Store the command code as an integer.

Jeff

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System