# Go performance and benchmarks

Measure Go string construction and allocation costs, with benchmark results and a public repository of runnable case studies.

Canonical HTML: https://vvivid.dev/tags/benchmarking/


A performance claim is easier to judge when you can run the code. The [string construction benchmark](/posts/go_string_concat_vs_string_builder/) compares `+=`, `strings.Builder`, and a pre-grown buffer. The [case study project](/projects/go-lang-case-study/) links the source and tests. Treat the reported numbers as measurements of that setup, then measure your own workload.


- [String Concatenation vs strings.Builder in Go](https://vvivid.dev/posts/go_string_concat_vs_string_builder/) · [Markdown](https://vvivid.dev/posts/go_string_concat_vs_string_builder/index.md) · 2026-06-13
  A small Go benchmark showing when repeated string concatenation becomes expensive and how strings.Builder changes the allocation profile.
- [Go Language Case Studies](https://vvivid.dev/projects/go-lang-case-study/) · [Markdown](https://vvivid.dev/projects/go-lang-case-study/index.md) · 2026-06-13
  A public collection of focused Go case studies, tests, and benchmarks for practical backend engineering topics.