stevej_buoyant
Re:Linkerd-tcp: A lightweight, service-discovery-aware, TLS-ing TCP lo...
on Thursday March 30, 2017 @12:29PM (#13996791)
We do not preserve source IP currently.
Re:Linkerd-tcp: A lightweight, service-discovery-aware, TLS-ing TCP lo...
on Thursday March 30, 2017 @12:15AM (#13992845)
So far latency has been comparable with other native load balancers: we've built performance profiles for nginx proxy_pass and haproxy to compare against although as we add features our numbers are starting to come down a bit.
We're still building our collection of tools for tracking down performance issues like lock contention, allocation hotspots, etc. I've had good luck finding cpu hotspots with linux perf and valgrind but less luck tracking down mutex holders and allocation hotspots. Any advice is welcome!
Re:Linkerd-tcp: A lightweight, service-discovery-aware, TLS-ing TCP lo...
on Wednesday March 29, 2017 @11:13PM (#13992575)
It's tough to compare the performance of the two systems because linkerd-tcp is not an HTTP proxy currently, it's a TCP proxy. That said, the resource footprint has been much lower than a finagle service. My first prototype, which had no fancy features like load balancing or metrics, was able to proxy a gigabit worth of traffic in less than a core on an older Ivy Bridge machine and used about 10Mb of RSS.
The biggest challenge has been learning to use the ownership system properly. It took me a few frustrating weeks to learn a new set of patterns and techniques for structuring code in a Rust-friendly method. Reading through the tokio code and example projects was really helpful in that regard.