Thats Great. I will look into this and check that in my project. Will return back with the results :)
On Wed, Oct 7, 2009 at 6:17 PM, [email protected] < [email protected]> wrote: > > Hi Pankraj, > > Here at nasza-klasa.pl we've developed a patch that I've described in > > http://groups.google.com/group/memcached/browse_thread/thread/31d34fbf4a3184ef# > The idea is to eagerly perform garbage collection each second, so that > the curr_item is always equal to the actuall number of not expired > elements. > Also we use this to monitor the real memory consumption of memcached > servers and were really happy to find out that we need two times less > memory than before the patch. > > [sorry if my message is repeated, but I've waited 5 minutes, and I > still do not see my reply] > > > On 6 Paź, 12:19, Pankaj Kumar <[email protected]> wrote: > > Hi, > > > > We are using Memcached Server for our caching module. We have a > > monitoring application which should raise an alram if the number of > > items in the cache gets below the actual value. Actually we have a > > certain number of objects whose count is fixed and we are storing it > > in cache as its getting updated every 30 secs. Now when we didn't get > > the update or our application that Populates this cache stops working, > > the objects in the cache will start expiring and we should raise an > > alarm for this. > > We thought of using curr_item of stat to check the current number of > > items in the cache, but even if the object is expired, its not > > updating it. When client application hits the cache server and it > > returns null as item has been expired then the count decreases by one. > > So this number doesn't represent the actual number of items in the > > cache. Can you please help me with this? Is there any other way to get > > the actual number of items in the cache at a given time? > > > > Thanks & regards, > > Pankaj > -- Thanx & Regards, Pankaj kumar Software Engr TCS India
