🤖 "Understanding" the Go Scheduler is code for a 💤-inducing saga about #Goroutines and the majestic #GMP 🌀 model – a thrilling tale of scheduling minutiae nobody asked for, sprinkled with enough disclaimers to make you question if the author even believes it. Spoiler alert: it's mostly recycled content, with a side of 'please correct me' humility. 🙄
https://nghiant3223.github.io/2025/04/15/go-scheduler.html #GoScheduler #RecycledContent #TechHumor #CodingSaga #HackerNews #ngated

Секреты дедлоков

Как-то раз я допустил в своем коде дедлок и пока выкатывал пул реквест с его фиксом думал “ах как бы было хорошо, если дедлоки определялись на этапе компиляции”. Я решил немного разобраться в этом вопросе и вот что выяснил… Узнать больше

https://habr.com/ru/companies/ozonbank/articles/908978/

#go #goroutine #goroutines #panic #deadlock #deadlocks #timer #дедлок #горутина #горутины

Finally got the mpb progress bar with #goroutines and goroutine limiting to work properly.

#golang #concurrency

https://go.0xfc.de/i02oju

Ah, yes, the epic 2025 standoff between the crab with delusions of zero-cost grandeur and the #gopher juggling #goroutines like it's Cirque du Soleil. 🦀🤹‍♂️ Meanwhile, #TypeScript is left in the corner wondering why it even bothered attending this backend brawl. 🤷‍♀️💻
https://effective-programmer.com/rust-vs-go-battle-for-the-backend-368f775de9fc #epicstandoff #crabvs #backendbrawl #HackerNews #ngated

Structured concurrency в языке Go

Горутины виснут непонятно почему, случайная запись в закрытый канал вызывает panic, нормально протестировать приложение вообще невозможно. Наверняка многие из вас сталкивались с такой проблемой: синтаксис языка Go вроде бы очень простой, можно сказать примитивный, да и горутины создаются элементарно, но при этом написать мало-мальски серьёзную программу, которая конкурентно что-то делает, внезапно оказывается не так-то просто. Чтобы не запутаться, люди придумали концепцию structured concurrency, которую можно применять и в Go. Читай или страдай

https://habr.com/ru/companies/karuna/articles/816677/

#go #goroutines #structured_concurrency

So I'm watching this premium #Go tutorial. The expert shows how fetching 3 URLs sequentially takes 2.1s, whereas running concurrently takes only... 400ms. Both "tests" in the same process. I'm pretty sure connection pooling, DNS caching, HTTP caching and so on contributed much more than #goroutines... And I thought using float32 for money, a few chapters back, was bad

@fsharponline

Can anyone show me the #fsharp equivalent of these concurrent #goroutines sharing a #connectionpool to #postgresql ?
https://gist.github.com/giuliohome/7ab1e57bd510b72f14faf0d95488a8de#file-db-go

Managed to reduce the exec time for 2023 day 23 part 2 from 513 seconds (~8.5 mins) to a stellar 0.310 seconds. Looking back at my commits these were the biggest leaps:

- By far the biggest leap: Shrink unique nodes to <= 64, then instead of a map simply use a `uint64` bitmask for boolean lookups (visited or not). Saves a lot of map accesses & assignments
- Prefer `int` when doing most calculations and comparisons, seems super optimized in the Go runtime

#go #golang #aoc2023 #goroutines

That said, running the exact squeezed single-core-optimized algorithm, but for multiple inputs on multiple cores simultaneously with 5 lines of code, feels absolutely awesome! 😎

#golang #go #goroutines #aoc2023

🌘 Go語言goroutines的缺點
➤ Go語言goroutines的缺點 - Skin的部落格
✤ https://blog.djha.skin/blog/the-down-sides-of-gos-goroutines/
近期作者對Go語言的隱含事件循環和協作與OS級執行緒之間的差異的決定有了新的看法。這個決定導致了幾個缺點，包括無法使用異常和無法在實時（掛鐘時間）同步任務。作者指出這些缺點是由於Go語言強調coroutines而產生的。此外，作者也討論了goroutines缺乏適當的堆疊祖先，導致無法保證對資源的生命週期，以及事件循環對任務調度的限制。
+ 對於Go語言的缺點有更深入的瞭解，值得進一步關注這些問題對開發人員和軟體設計有何影響。
+ 這篇文章解釋了Go語言在使用goroutines時可能出現的問題，對於想要使用這種語言的開發人員來說是一個很好的警示。
#Go語言 #goroutines #程式設計

With this, I shall have Fearless Concurrency in Go!

#golang #go #concurrency #goroutines #threads #rust

Interesting explanation why #VirtualThreads are similar to #goroutines and not to coroutines and green threads.

https://en.m.wikipedia.org/wiki/Talk:Virtual_threads

^-----

toot to amplify upthread toot, by adding content hashtags:

#Golang
#programming
#latency
#instrument
#instrumentation
#APIs
#measure
#measuring
#metrics
#stats
#monitoring
#observability
#perf
#perftools
#performance
#scale
#scaling
#scalability
#benchmarks
#tuning
#regression
#optimize
#optimization
#time
#compute
#tradeoffs
#software
#concurrency
#threads
#multithreading
#goroutines

as a fan of oldskool dystopic/apoc fiction & drama TV (esp from the 60s to 80s, & UK/Euro) let me just say Meta's choice of the Threads name is terrible... & PTSD-inducing

as a decades-long programmer with plenty of scars from doing & seeing multi-threaded programming at scale, well, let me just say Meta's choice of the Threads name is also terrible... & PTSD inducing

#Meta
#Threads

#programming
#multithreading
#concurrency
#parallelism
#threading
#fibers
#coroutines
#goroutines
#processes

whenever I hear someone talk about using Meta/Facebook's new Threads I think, "Nah I'll just stick with Golang's channels-and-goroutines model instead, thanks!"

#Go
#Golang
#channels
#goroutines
#threading
#parallelism
#concurrency

#Threads
#Facebook
#Meta

@JorgeStolfi @xenotar I see a benefit in the usage of interfaces for unit testing even the ability to have #goroutines in most cases can make the need of an OS obsolete for most toy projects.

Goroutines Make Concurrency (Almost) Easy https://blog.teamtreehouse.com/goroutines-concurrency #concurrency #goroutines #channel #golang

- Go handles this problem by bringing another layer between the application and the kernel: the runtime. It uses a virtual entity (commonly referred to as P) which contains a queue of #goroutines to run, which is then mapped to OS threads.

In less than 2 months @docker@twitter.com, I already code in @golang@twitter.com @SwiftLang@twitter.com #CSharp @reactjs@twitter.com
Develop front & back features, use #goroutines with #mutex & extend a CLI 🤩
Wanna join us? We’re looking for Front & Backend developers
https://grnh.se/cff130f81
https://grnh.se/31ed2da11