multiple pools in Java
mybrid at datarebels.com
Wed Apr 6 17:47:17 PDT 2005
Happy Thursday! Thanks so much for replying.
Ok, here is more detail. We are having excellent success with this
very well designed product. One problem we are having is that large
objects only have a cache hit rate of 45% while small objects are 90%
plus. We speculate the root cause is that our web site uses objects of
every size imaginable and that there is not enough slab space for large
sized objects. We'd like to experiment with segmenting by writing
objects larger than X to one cache pool where we tune X.
Any thoughts on this would be greatly appreciated. JFYI, your cache
has helped us nearly double our bandwidth and we really truly appreciate
Brad Fitzpatrick wrote:
>Why don't you just make one pool that's twice as big, then?
>If a node in a pool dies, the memcached client just routes around it and
>spreads the load to the nodes that are still alive.
>On Tue, 5 Apr 2005, Mybrid Spalding wrote:
>> Greetings from a first-time poster. I'm currently using the Java
>>client to connect to memcached. For robustness reasons I'm thinking of
>>segementing traffic to different caches. That way if one cache pool goes
>>down I can route to another. However, reading the Java docs its not
>>obvious to me how to or a good strategy.
More information about the memcached