8 ms·
Putting aside what seems to be an amazing new product, but the blog post showing the results are also downplaying what (to me at least) seems to be a 25% or mor
by fernandopj 4y ago
Putting aside what seems to be an amazing new product, but the blog post showing the results are also downplaying what (to me at least) seems to be a 25% or more increase in latency.
- worldsoup 4y agoDragonfly employee here...where are you seeing the 25% increase in latency? that's not the case so want to make sure the post is not confusing.
- reconditerose 4y agoI wouldn't take their latency numbers too seriously since their measure isn't relative to the throughput. It's not always obvious, but the latency of high performance is tightly coupled with throughput. The latency of high performance systems is the server side execution time (for Redis that is a couple of microseconds), the network hop (probably a couple of hundred microseconds), and the congestion on the server (this is the time it takes the server to actually getting around to processing your request, since the server probably needs to handle other requests first before getting around to yours). The congestion, is directly tied to the throughput. The most useful measurement I've seen is you pick a latency target, and evaluate how many QPS you can send to the server that meets that latency target. That gives a fairly simple dimension to compare to.