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

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.