I am working with this Memcached cluster which reports about 70% of the objects put in end up being evicted. I have a TTL of 1 hr for all objects I put in. Looking at my hit/miss metrics I've realized that in time my hit rate has got much better while evictions increase. Misses have increased at a very slow rate compared to my hit rate increase.
>From the bytes written stat I know that I'd need about 5 times more Memcached capacity to hold of the bytes I place in Memcached today. But given my hit rate success I don't think it makes sense to me to increase my Memcached capacity 5 times. I'm guessing that allowing my cache to discard data based on evictions rather than expirations is a lot more cost effective as long as the hit rate doesn't get affected. I'd like to know, how much more expensive is for Memcached to perform evictions rather than expirations? Is there any other major negative effect I should take in account about relying on evictions such as thread contention during the eviction process or something else that could affect my app's performance? One more thing, I see some entries in my memcached.log but they don't have a time stamp which makes it very difficult to tie those entries back to my app logs and all the other logs. Is there a way to configure Memcached to log timestamps along with each message? Claudio -- --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
