EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Memory Problem related to CA?
From: "Jeff Hill" <[email protected]>
To: "'Schoeneburg, Bernd'" <[email protected]>, <[email protected]>
Date: Fri, 14 Mar 2008 14:18:26 -0600
Hello Bernd,

Yes, to avoid problems with fragmentation, the CA server does have several
free memory pools. As you suspect, the free lists that it uses are not
returned to the system pool, and so its memory usage high water mark will
persist even if the client load decreases. One can examine how much memory
it has in its pocket using the "casr" command specifying higher interest
levels.

With R3.13 there are more raw malloc/calloc requests in the ca server (that
don't use a free list) and so there is greater potential for fragmenting the
system memory pool. More recent versions of vxWorks use a best fit memory
allocation scheme so fragmentation of the system memory pool is less common,
but of course memory allocation overhead is also higher. You can examine
some statistics of the system memory pool with the "memShow" command.

> Can the channel access pool become fragmented? 

Probably not because it uses free lists - each of them dedicated to a
particular size of block that is needed.

Jeff

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Schoeneburg, Bernd
> Sent: Friday, March 14, 2008 10:20 AM
> To: [email protected]
> Subject: Memory Problem related to CA?
> 
> Hi all,
> on some IOCs we see that the free memory becomes less and less.
> Especially when we restart our channel archiver, the free memory in the
> IOCs becomes much less.
> My possible explanation for this is that channel access has not a free
> memory block of the desired (big) size in its private pool, so that
> additional memory from the system pool is allocated - and never free'd.
> Is this possible? Can the channel access pool become fragmented? If YES:
> Is there a solution for this in later versions? Or a patch?	
> 
> We are using Epics 3.13.10 with vxWorks 5.3.1 on mvme162-532A (16 MB)
> 
> Thank you
> 
> Bernd


Replies:
Re: Memory Problem related to CA? Schoeneburg, Bernd
References:
Memory Problem related to CA? Schoeneburg, Bernd

Navigate by Date:
Prev: Re: Memory Problem related to CA? Paul Sichta
Next: RE: Memory Problem related to CA? Jeff Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Memory Problem related to CA? Jeff Hill
Next: Re: Memory Problem related to CA? Schoeneburg, Bernd
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  <20082009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·