News for hackers. Stuff that matters.
Re:How Fast can A Single Instance of Redis be? by lossolo on Tuesday June 18, 2019 @03:22PM (#20217272)
Well, to be honest if you are IO/network bound and kernel TCP stack is the bottleneck then user space networking like DPDK can help in every application. It depends on application but sometimes additional complexity of introducing DPDK is just not worth it, and just spinning another instance/server is a better choice. Look also at Seastar used in ScyllaDB with and without DPDK numbers.

Just remember you need to give DPDK one whole NIC and it's using polling so 100% CPU usage on polling cores.

Re:How Fast can A Single Instance of Redis be? by jdsully on Tuesday June 18, 2019 @05:50PM (#20218819)
DPDK does poll but you can have it sleep in low traffic situations. At the expense of a little extra latency.
Re:How Fast can A Single Instance of Redis be? by hinkley on Tuesday June 18, 2019 @08:37PM (#20219874)
I always figured the right solution here is a queue that sends any time the request queue is over N elements or every M microseconds, whichever happens first. Haven’t seen many implementations though.

Nagle’s algorithm for the oldest, maybe a couple others, possibly some code I’ve written.

Re:How Fast can A Single Instance of Redis be? by shaklee3 on Wednesday June 19, 2019 @12:59AM (#20220908)
DPDK has had ways to not use 100% of the CPU for polling for many years.

https://doc.dpdk.org/guides-16.04/sample_app_ug/l3_forward_p...

Re:How Fast can A Single Instance of Redis be? by zerd on Tuesday June 18, 2019 @09:19PM (#20220090)
I wonder how the performance compares with pedis [1], which is based on Seastar/ScyllaDB.

https://github.com/fastio/pedis