←back to thread

Go Optimization Guide

(goperf.dev)
482 points jedeusus | 5 comments | 3/31/2025, 8:29:00 PM | HN request time: 1.738s | source
1. neillyons ◴[4/1/2025, 5:33:00 AM] No.43543171[source]▶

Curious to know what people are building where you need to optimise like this? eg Struct Field Alignment https://goperf.dev/01-common-patterns/fields-alignment/#avoi...

replies(2): >>43543293 #>>43543824 #
2. dundarious ◴[4/1/2025, 5:56:00 AM] No.43543293[source]▶

False sharing is an absolutely classic Concurrency 101 lesson, nothing remarkable about it.

3. kubb ◴[4/1/2025, 7:24:00 AM] No.43543824[source]▶

Something that shouldn’t be written in a GC language.

replies(2): >>43544207 #>>43544263 #
4. piokoch ◴[4/1/2025, 8:28:00 AM] No.43544207[source]▶

I don't think GC has anything to do here, doing manual memory allocation we might hit the same problem.

5. Cthulhu_ ◴[4/1/2025, 8:34:00 AM] No.43544263[source]▶

GC is not relevant in this case, it's about whether you can make structs fit in cache lines and CPU registers. Mechanical sympathy is the googleable phrase. GC is a few layers further away.