4 ms·
I wonder if anyone has tried it with Solarflare?
by easytiger 12y ago
I wonder if anyone has tried it with Solarflare?
- neomantra 12y agoSolarflare has a whitepaper on accelerating memcached: http://10gbe.blogspot.com/2014/12/memcached-3x-faster-than-intel.html http://10gbe.blogspot.com/2014/12/memcached-3x-faster-than-i... I just whipped this up in 5 minutes and didn't do much of the tuning there (e.g. no isolcpus or interrupt changes), but here's a single-client 1024-byte SET redis-benchmark running against localhost with and without TCP Loopback Acceleration... redis 2.8.4 on a dual E5-2630 @ 2.30GHz, card is SFN5122F but this is all loopback. I'm not claiming anything and just doing it because somebody pondered... * plain jane /usr/bin/redis-server redis-benchmark -t set -q -n 1000000 -d 1024 -c 1 SET: 21258.96 requests per second * unaccelerated server, unaccelerated client numactl --physcpubind 1,3,5 --preferred 1 /usr/bin/redis-server numactl --physcpubind=7,9 --preferred 1 redis-benchmark -t set -q -n 100000 -d 1024 -c 1 SET: 14293.88 requests per second * TCP loopback accelerated server, unaccelerated client EF_NAME=hn EF_TCP_SERVER_LOOPBACK=2 EF_TCP_CLIENT_LOOPBACK=2 onload -p latency numactl --physcpubind 1,3,5 --preferred 1 /usr/bin/redis-server numactl --physcpubind=7,9 --preferred 1 redis-benchmark -t set -q -n 100000 -d 1024 -c 1 SET: 25967.28 reque sts per second * TCP loopback accelerated server, accelerated client EF_NAME=hn EF_TCP_SERVER_LOOPBACK=2 EF_TCP_CLIENT_LOOPBACK=2 onload -p latency numactl --physcpubind 1,3,5 --preferred 1 /usr/bin/redis-server EF_NAME=hn onload -p latency numactl --physcpubind=7 --preferred 1 redis-benchmark -t set -q -n 1000000 - d 1024 -c 1 oo:redis-benchmark[13454]: Sharing OpenOnload 201405-u1 Copyright 2006-2012 Solarflare Communications, 2002-2005 Level 5 Networks [4,hn] SET: 96098.41 requests per second Edit: formatting fixes
- easytiger 12y agoNot bad considering its "for free". Thanks a lot for the post