dormando

7 ms·

61.
by dormando 8y ago
I wrote the current version of OSS memcached. I don't know how elasticache is configured, but as I said memcached itself can definitely saturate the network from that instance. Either the version they run is too old or it's miscon
62.
by dormando 8y ago
I characterize it as slow because I know it can saturate the packet rate AWS gives it with software memcached. If the packet rate were much higher then you might win out. The only reason why you can claim 9x latency is because you've s
63.
by dormando 8y ago
How is elasticache so slow? what instances does it run on? edit: r4.4xlarge as per the link. 16vcpu? You should be able to beat on latency but beating on throughput means elasticache is misconfigured, likely. Or you're putting on way t
64.
by dormando 8y ago
This seems old (2013ish?). There're newer "key/value on FPGA" papers that're more modern. If memcached papers have one thing in common, it's an uncanny ability to get the comparison software to run as slowly as
65.
by dormando 8y ago
Paper seems to miss the modified-2Q algorithm which was in memcached as of the cited 1.4.33 (became default in 1.5.0). Has very different performance characteristics than straight LRU. Still need to give a more thorough read, but spotting o
66.
by dormando 9y ago
I worked on the fastly varnish fork. None of this is accurate. Definitely not "because of phk influence". Most of the details are obviously secret, but occasionally when we found something architecturally concerning I'd talk