{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Container-aware GOMAXPROCS: What it is and Why It's Important","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/df4bc4d5\"></iframe>","width":"100%","height":180,"duration":597,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/container-aware-gomaxprocs-what-it-is-and-why-its-important.\n             In this post, we will dive into how Go schedules goroutines, how that scheduling interacts with container-level CPU controls, and how Go can perform better. \n            Check more stories related to programming at: https://hackernoon.com/c/programming.\n            You can also check exclusive content about #go, #golang, #gomaxprocs, #go-1.25, #go-new-update, #goroutines, #container-orchestration, #hackernoon-top-story,  and more.\n            \n            \n            This story was written by: @Go. Learn more about this writer by checking @Go's about page,\n            and for more stories, please visit hackernoon.com.\n            \n                \n                \n                Go 1.25 includes new container-aware `GOMAXPROCS` defaults. These defaults provide more sensible default behavior for many container workloads. They also avoid throttling that can impact tail latency, improving Go’s out-of-the-box production-readiness.\n        \n        ","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}