Top all-time · #10319
Tit Petric
Personal blog · scene-si.orgprogrammingweb
Tit Petric writes Office Hours, a personal blog at scene-si.org about programming and web. Since 2015, 7 different Hacker News readers have linked it 38 times, most often “Benchmarking Go programs”. It is still writing: the last post was on 2026-06-09, and you can follow it by feed.
Too few sampled comments (1) to say how often HN recommends it.?
Why HN links it
HN readers link this Go post to explain that the built-in benchmark tool reports bytes allocated per call, which is why some Go libraries aim for zero allocations.
Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Go focused best practice column
Most-linked posts?
- Benchmarking Go programs4 people · 4 mentions · first linked 2017-06-06
What Hacker News says?
It's a common optimization in Go. The benchmark tool that ships with go allows reporting of bytes allocated per call. Many webserver frameworks in Go strive for 0 allocs so as a user of the library, you know it won't cause extra garbage. https://scene-si.org/2017/06/06/benchmarking-go-programs/
Comment linking /2017/06/06/benchmarking-go-programs/
on “Show HN: Molecule – Streaming, zero-allocation protobuf decoding in Go”Submitted Setting up a remote digital workspace as a story · 15 points
HN discussionSubmitted How to pass docker.sock to your containers while keeping security as a story · 4 points
HN discussionSubmitted Docker: migrating containers between hosts, portable environments as a story · 4 points
HN discussionSubmitted Interfaces in Go – Tit Petric as a story · 3 points
HN discussionSubmitted Benchmarking Go programs as a story · 3 points
HN discussionSubmitted Store config in the environment (golang, docker, 12fa) as a story · 3 points
HN discussionSubmitted Advanced Golang Tips and Tricks (pt.2) as a story · 3 points
HN discussionSubmitted Deploying Go (or Node, or Ruby,) Applications in Docker as a story · 3 points
HN discussionSubmitted Waiting on Goroutines – Tit Petric as a story · 2 points
HN discussionSubmitted Writing Great Go Code – Tit Petric as a story · 2 points
HN discussionSubmitted Writing Great Go Code – Tit Petric as a story · 2 points
HN discussionSubmitted Error handling in Go as a story · 2 points
HN discussionSubmitted MySQL tips for developers as a story · 2 points
HN discussionSubmitted Things I Learned in DevOps in Q1 2017 – Tit Petric as a story · 2 points
HN discussionSubmitted Docker, you lied to me as a story · 2 points
HN discussionSubmitted Golang tips and tricks, pt. 3 as a story · 2 points
HN discussionSubmitted Dependency Injection patterns in Golang (adv. go pt. 3) as a story · 2 points
HN discussionSubmitted Network timeouts with Docker containers? Let me show you how to start debugging as a story · 2 points
HN discussionSubmitted Run Node.js Anywhere Using Docker and Nexe as a story · 2 points
HN discussionSubmitted Testing PHP code using Docker as a story · 2 points
HN discussionSubmitted Go tips and tricks: almost everything about imports as a story · 1 points
HN discussionSubmitted Waiting on Goroutines – Tit Petric as a story · 1 points
HN discussionSubmitted Elegant code and Go as a story · 1 points
HN discussionSubmitted Things to know about HTTP in Go as a story · 1 points
HN discussionSubmitted Benchmarking Go programs as a story · 1 points
HN discussionSubmitted Benchmarking Go programs as a story · 1 points
HN discussionSubmitted Auto-Scaling a Docker Swarm on DigitalOcean as a story · 1 points
HN discussionSubmitted Calling Go Functions from LUA – Tit Petric as a story · 1 points
HN discussionSubmitted Building your own build status indicator with GoLang and RPi3 as a story · 1 points
HN discussion