Hi Ed, On Friday, September 21, 2012 5:48:47 PM UTC+3, Ed Hickey wrote: > > The write up on the main page describes "small" chunks of data. > > Does anyone have an idea of how much data can be practically stored in > memcached? We are looking at upwards of several millions rows of small > data (store/product/price). > > Are we better off with an in-memory database instead? > > Your thoughts? >
Use memcached if all your data fits RAM. Otherwise two options exist: * shard your data into a cluster of memcached instances, so each memcached instance keeps part of data, which fits available RAM on the host it is running. * use go-memcached ( https://github.com/valyala/ybc/tree/master/apps/go/memcached ). It is optimized for very large caches exceeding available RAM size by multiple orders of magnitude. And don't use cache as primary storage. Keep in mind - cache may evict arbitrary objects at arbitrary time due to arbitrary reasons.
