Re: Resident Memory larger then expected

The RESIDENT segment is more than just the buffer cache. For example, the lock table and the data dictionary, data distribution, stored procedure, statement and other static caches are all stored in the resident segment. Also if you have set RESIDENT to a value other than zero or one on HPUX (I know you are using Solaris) the first virtual segment is folded into the resident segment to minimize the number of shared memory handles used. Art Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) See you at the 2010 IIUG Informix Conference April 25-28, 2010 Overland Park (Kansas City), KS www.iiug.org/conf Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Fri, Dec 11, 2009 at 6:55 AM, Habichtsberg, Reinhard < RHabichtsberg@arz-emmendingen.de> wrote: > Hi all, > > in onconfig I set > > BUFFERPOOL> > size=2K,buffers=20000,lrus=8,lru_min_dirty=20.000000,lru_max_dirty=30.000000 > . > > In the message log I see: > Memory sizes:resident:570368 KB > > In earlier versions of IDS the formular was BUFFERS x 2 = Size in KB. I had > expected memory size resident: 40000 KB. > > What's the reason for the difference and how can I handle it. > > IDS11.50FC5W4 in Solaris 10 > > TIA, > Reinhard. > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list >