4 ms·
Aggressive GC latency improvements, like the ones Go is making, virtually always negatively affect throughput. For example, Azul C4 has lower throughput than Ho
by pcwalton 11y ago
Aggressive GC latency improvements, like the ones Go is making, virtually always negatively affect throughput. For example, Azul C4 has lower throughput than HotSpot (at least per the numbers cited in the paper). There's no free lunch in GC.
- FooBarWidget 11y agoBut I would argue that most people who use Go, use it to write user-facing server apps, or at least server apps in which response time is an important metric. I don't know anybody who uses Go to primarily write batch jobs where throughput matters more than latency.
- mike_hearn 11y agoYeah, but that's circular - if you did want to write a high performance batch job, maybe you wouldn't use Go because of the GC. And hi by the way ;)