Thanks Perrin, it's definitely an alternative!
Hans On Tue, Apr 28, 2015 at 3:28 PM, Perrin Harkins <phark...@gmail.com> wrote: > It does write to disk, so maybe it's not appropriate for your use. It is > widely used in embedded systems though. > > On Tue, Apr 28, 2015 at 9:08 AM, Hans Kramer <jlam.kra...@gmail.com> > wrote: > >> Doesn't BerkelyDB write to disk? (of course I could use a tmpfs...... >> hmmm ) >> And I us the auto expire of items in memcache.... >> >> Thanks for the tip, I definitely will consider it! >> >> Hans >> >> On Tue, Apr 28, 2015 at 2:43 PM, Perrin Harkins <phark...@gmail.com> >> wrote: >> >>> You might want to look at alternatives in that kind of setup. For >>> example, BerkeleyDB is quite a bit faster than memcached when your cache is >>> just on one local system. The advantages of memcached come into play when >>> you have a large cache across multiple machines. >>> >>> - Perrin >>> >>> On Mon, Apr 27, 2015 at 6:00 AM, Hans Kramer <jlam.kra...@gmail.com> >>> wrote: >>> >>>> Hi, >>>> >>>> I am using memcached on a system with very modest RAM: 64Mb to be >>>> precise (an Artila Matrix 504). >>>> I have specified -M 1 -t 1 to reduce the memory allocated by memcached. >>>> Now RSS is always modest and around an explainable value, however, VSZ >>>> is at least 20Mb and with every >>>> thread I add VSZ increases with at least 6 Mbytes. If I understand this >>>> correctly, this relative "high" VSZ, increases the oom_score >>>> a lot. Hence I would like to reduce unnecessary alloc as much as >>>> possible. >>>> I have briefly looked at the memcached source and I cannot any >>>> significant mallocs. Is this perhaps coming from the libevent >>>> library? >>>> >>>> Any insights will be helpful. >>>> >>>> Kind regards >>>> >>>> Hans >>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "memcached" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to memcached+unsubscr...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> >>> --- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "memcached" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/memcached/c-jJSFKZ1d0/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> memcached+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "memcached" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to memcached+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "memcached" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/memcached/c-jJSFKZ1d0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > memcached+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
