←back to thread

Go Optimization Guide

(goperf.dev)
480 points jedeusus | 1 comments | 31 Mar 25 20:29 UTC | HN request time: 0.236s | source
Show context
kevmo314 ◴[31 Mar 25 23:35 UTC] No.43541214[source]▶
Zero-copy is totally underrated. Like the site alludes to, Go's interfaces make it reasonably accessible to write zero-copy code but it still needs some careful crafting. The payoff is great though, I've often been surprised by how much time is spent allocating and shuffling memory around.
replies(1): >>43542637 #
1. jasonthorsness ◴[01 Apr 25 03:46 UTC] No.43542637[source]▶
I once built a proxy that translated protocol A to protocol B in Go. In many cases, protocol A and B were just wrappers around long UTF-8 or raw bytes content. For large messages, reading the content into a slice then writing that same slice into the outgoing socket (preceded and followed by slices containing the translated bits from A to B) made a significant improvement in performance vs. copying everything over into a new buffer.

Go's network interfaces and slices makes this kind of thing particularly simple - I had to do the same thing in Java and it was a lot more awkward.