[GH-ISSUE #257] CPU throttling for containerized Go applications explained #223

Closed
opened 2026-05-05 11:32:38 -06:00 by gitea-mirror · 2 comments
Owner

Originally created by @enocom on GitHub (Nov 10, 2024).
Original GitHub issue: https://github.com/enocom/gopher-reading-list/issues/257

https://kanishk.io/posts/cpu-throttling-in-containerized-go-apps/

Originally created by @enocom on GitHub (Nov 10, 2024). Original GitHub issue: https://github.com/enocom/gopher-reading-list/issues/257 https://kanishk.io/posts/cpu-throttling-in-containerized-go-apps/
gitea-mirror 2026-05-05 11:32:38 -06:00
  • closed this issue
  • added the
    advanced
    label
Author
Owner

@pellared commented on GitHub (Nov 22, 2024):

I prefer https://kupczynski.info/posts/go-container-aware because of its more concise and also describes OOMKilled and not only CPU throttling.

<!-- gh-comment-id:2493472835 --> @pellared commented on GitHub (Nov 22, 2024): I prefer https://kupczynski.info/posts/go-container-aware because of its more concise and also describes OOMKilled and not only CPU throttling.
Author
Owner

@enocom commented on GitHub (Mar 21, 2025):

Dupe of https://github.com/enocom/gopher-reading-list/issues/267.

<!-- gh-comment-id:2743626707 --> @enocom commented on GitHub (Mar 21, 2025): Dupe of https://github.com/enocom/gopher-reading-list/issues/267.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gopher-reading-list#223
No description provided.