How we tracked down a Go 1.24 memory regression (datadoghq.com) | HN Screenshots

YHacker Newsscreenshots

Screenshot of datadoghq.com: How we tracked down a Go 1.24 memory regression

First screen, captured 1 year ago.

Looks similar

Screenshot of heyoncall.com: Fixing a kubelet memory leak in Kubernetes 1.36

Fixing a kubelet memory leak in Kubernetes 1.36 (heyoncall.com)

68 points by compumike 3 months ago | 13 comments

Screenshot of adriacabeza.github.io: Analyzing the codebase of Caffeine, a high performance caching library

Analyzing the codebase of Caffeine, a high performance caching library (adriacabeza.github.io)

246 points by synthc 1 year ago | 44 comments

Screenshot of about.gitlab.com: How we decreased GitLab repo backup times from 48 hours to 41 minutes

How we decreased GitLab repo backup times from 48 hours to 41 minutes (about.gitlab.com)

563 points by immortaljoe 1 year ago | 236 comments

GitLab engineering blog post explaining how fixing a 15-year-old Git function bottleneck cut repository backup times from 48 hours to 41 minutes.

git gitlab backups performance-optimization

Screenshot of coder.com: We improved the performance of a userspace TCP stack in Go

We improved the performance of a userspace TCP stack in Go (coder.com)

214 points by infomaniac 2 years ago | 106 comments

Screenshot of deductive.ai: Datadog, thank you for blocking us

Datadog, thank you for blocking us (deductive.ai)

62 points by binarylogic 9 months ago | 29 comments

Screenshot of deductive.ai: Datadog, Thank You for Blocking Us

Datadog, Thank You for Blocking Us (deductive.ai)

15 points by gpi 9 months ago | 0 comments