Thanks a lot, Dormando. Will do try to optimize with Ketama first from the
client side.
On Thursday, March 21, 2019 at 2:49:59 PM UTC+8, Dormando wrote:
>
> ketama's just fine. Optimize for problems you have or can prove.
>
> The default in newer versions is murmur. I keep forgetting that AWS
ketama's just fine. Optimize for problems you have or can prove.
The default in newer versions is murmur. I keep forgetting that AWS
elasticache is stuck on that old version. Also beware they seem to have
some bugs. If you run into trouble just run your own instances; it's not
too hard.
On Wed,
Thanks a lot, Dormando!
I'm using KETAMA_HASH at the client side, didn't go for CRC_HASH as per the
Java Doc it says CRC_HASH can be slower in performance (and we are only
having Java client, so no need to support for multiple platforms). We only
have max 10 nodes of Memcached, but we want to
You don't need to worry about the server one at all. They don't need to
match up either; on the server side it's just for the hash table. The
default is fine. I only left jenkins in as a "just in case", too.
I don't think it matters that much for clients either. There're very few
buckets involved
Hi,
I'm quite an amateur on Memcached, please excuse me if my understanding is
not correct. I'm trying to connect to AWS ElastiCache Memcached servers
from my Spring service. As per my understanding cache key hashing is done
at two locations.
1. client side to decide the Memcache node
2. at
