An FPGA-based In-line Accelerator for Memcached (2013) [pdf]
1–10 of 34 posts
Re: An FPGA-based In-line Accelerator for Memcached (2013) [pdf]
#2These kind of optimisations will become more common as we near the end of Moore's law.
Re: An FPGA-based In-line Accelerator for Memcached (2013) [pdf]
#3This 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 possible. 100k ops/sec/core is what you get when using a single client connection with blocking I/O. Using more clients (as per a normal prod setup) or pipelining queries is more like 1m ops+/core, with writes scaling worse than reads. In production it's easy to get some level of pipelining (multigets, clustered keys, etc), since you're rarely just fetching a key and then blocking.
A much better FPGA paper would show scales of at what level the syscall overhead becomes most of the CPU usage, as well as any measured latency improvements. I think some of the other papers address latency at least.
In reality it hardly matters. If you're hitting memcached hard enough with tiny values for it to matter, ensuring keys are clustered and pipelined is a lot less maintenance overhead than deploying FPGA's.
Re: An FPGA-based In-line Accelerator for Memcached (2013) [pdf]
#4Our startup is working on accelerators using FPGAs on AWS including memcached.
Using a single AWS F1 (FPGA) instance, our Memcached accelerator achieves over 11 million ops/sec at less than 300 microsecond latency. Compared to ElastiCache, the AWS-managed CPU Memcached server, our Memcached accelerator offers 9X better throughput, 9X lower latency, and 10X better throughput/$.
We need to batch multiple requests per Ethernet packet to get around packet per sec rate limiting on AWS. See more details here: https://www.legupcomputing.com/blog/index.php/2018/05/01/dee...
If anyone is interested we would love to hear from you, we will be showing off an online demo later this week.
FPGAs are great for processing data at 10Gbps line rate with low latency. They are also good for compute tasks like compression and encryption.
Re: An FPGA-based In-line Accelerator for Memcached (2013) [pdf]
#5Our startup is working on accelerators using FPGAs on AWS including memcached. Using a single AWS F1 (FPGA) instance, our Memcached accelerator achieves over 11 million ops/sec at less than 300 microsecond latency. Compared to ElastiCache, the AWS-managed CPU Memcached server, our Memcached accelerator offers 9X better throughput, 9X lower latency, and 10X better throughput/$. We need to batch multiple requests per E…
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 too much set traffic (think I saw you set the bench to 1:1 ratio of gets to sets?)
Re: An FPGA-based In-line Accelerator for Memcached (2013) [pdf]
#6Our startup is working on accelerators using FPGAs on AWS including memcached. Using a single AWS F1 (FPGA) instance, our Memcached accelerator achieves over 11 million ops/sec at less than 300 microsecond latency. Compared to ElastiCache, the AWS-managed CPU Memcached server, our Memcached accelerator offers 9X better throughput, 9X lower latency, and 10X better throughput/$. We need to batch multiple requests per E…
really wish AWS supported Ethernet on fpga
Re: An FPGA-based In-line Accelerator for Memcached (2013) [pdf]
#7Our startup is working on accelerators using FPGAs on AWS including memcached. Using a single AWS F1 (FPGA) instance, our Memcached accelerator achieves over 11 million ops/sec at less than 300 microsecond latency. Compared to ElastiCache, the AWS-managed CPU Memcached server, our Memcached accelerator offers 9X better throughput, 9X lower latency, and 10X better throughput/$. We need to batch multiple requests per E…
About to congratulate you that you are about to make competition to Alibaba.com.
On our side, maxing the IOPS was the easy part. The hard one was to marry the protocol with converged/deterministic Ethernet with RDMA. We were split in between "one request, one frame/packet burst" vs "all requests are somehow smartly aligned with frames by stateful logic." The first one was surprisingly susceptible to performance artifacts due to varying round trip latency of few microseconds, thus it was possible to get packets in transit being dropped due to receiving NIC (a top tier hardware) being momentarily overloaded.
You have an advantage of being DC provider independent, and can jump the AWS ship whenever you want. Alibaba's solution will be tied to its infrastructure with its very expensive RDMA capable network.
Re: An FPGA-based In-line Accelerator for Memcached (2013) [pdf]
#8Our startup is working on accelerators using FPGAs on AWS including memcached. Using a single AWS F1 (FPGA) instance, our Memcached accelerator achieves over 11 million ops/sec at less than 300 microsecond latency. Compared to ElastiCache, the AWS-managed CPU Memcached server, our Memcached accelerator offers 9X better throughput, 9X lower latency, and 10X better throughput/$. We need to batch multiple requests per E…
I am the co-founder of Plunify. We have an ML software solution (InTime) that optimizes FPGA design by tuning the parameters of the compilation, i.e. synthesis, P&R. I don't know much about memcached accelerators but if it is a performance driven application, like HFT, I believe we can make it go even faster, i.e. increase the FMax. I read from your website that you are using Intel PSG devices. We often see designers using seeds to close timing or optimize the timing, but that is leaving performance on the table. For more details: https://support.plunify.com/en/2018/04/17/compare-timing-per...
Happy to talk more at kirvy@plunify.com if you are interested. Congrats on getting a seed round from Intel Capital!
Re: An FPGA-based In-line Accelerator for Memcached (2013) [pdf]
#9Our startup is working on accelerators using FPGAs on AWS including memcached. Using a single AWS F1 (FPGA) instance, our Memcached accelerator achieves over 11 million ops/sec at less than 300 microsecond latency. Compared to ElastiCache, the AWS-managed CPU Memcached server, our Memcached accelerator offers 9X better throughput, 9X lower latency, and 10X better throughput/$. We need to batch multiple requests per E…
I am the co-founder of Plunify. We have an ML software solution (InTime) that optimizes FPGA design by tuning the parameters of the compilation, i.e. synthesis, P&R. I don't know much about memcached accelerators but if it is a performance driven application, like HFT, I believe we can make it go even faster, i.e. increase the FMax. I read from your website that you are using Intel PSG devices. We often see designers…
Interesting, what synthesis settings have you found have the most impact? I have also seen FPGA designers trying different seeds when closing timing.
In this case, AWS provides an FPGA shell for external interfaces that has a maximum clock frequency of 250MHz. We have been able to meet this timing constraint without many issues. But we will keep you in mind for the Intel FPGA boards we are working with now.
Re: An FPGA-based In-line Accelerator for Memcached (2013) [pdf]
#10Our startup is working on accelerators using FPGAs on AWS including memcached. Using a single AWS F1 (FPGA) instance, our Memcached accelerator achieves over 11 million ops/sec at less than 300 microsecond latency. Compared to ElastiCache, the AWS-managed CPU Memcached server, our Memcached accelerator offers 9X better throughput, 9X lower latency, and 10X better throughput/$. We need to batch multiple requests per E…
really wish AWS supported Ethernet on fpga
There aren't Ethernet interfaces (transceivers, PCS/PMA, MAC) on the AWS FPGAs?