Top all-time · #4507
Morsing's Blog
Personal blog · morsmachine.dkprogrammingsystems
Morsing's Blog is a personal blog at morsmachine.dk about programming and systems. Since 2013, 17 different Hacker News readers have linked it 19 times, most often “The Go scheduler – Morsing's blog”. No feed was found, so read it on the site itself.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link this blog as a source on the Go scheduler and goroutine scheduling, including how Go moves coroutines between threads and how it handles blocking I/O.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- The Go scheduler – Morsing's blog5 people · 5 mentions · first linked 2016-08-12
- The Go 1.1 scheduler4 people · 4 mentions · first linked 2013-07-01
- TCP is an underspecified two-node consensus algorithm2 people · 2 mentions · first linked 2018-03-19
- The Go netpoller (2013)2 people · 2 mentions · first linked 2015-10-18
What Hacker News says?
> There are no asynchronous operations in that go model, everything is synchronous. You are the second person saying this, and i have to admit i am really confused by this statement. From my understanding, golang does not expose an asyncio interface, but this doesn't meant that golang runtime doesnt perform io operations asynchronously. So golang expose async operation through a synchronious interface, which is what…
Comment linking /go-scheduler
on “Zero-cost futures in Rust”Submitted The Go 1.1 scheduler as a story · 139 points
HN discussionYou can move the the co-routine onto another thread. The go scheduler does this: https://morsmachine.dk/go-scheduler There isn't really a "comparison" here. Co-routines/fibers could behave exactly like nginx does for IO or not at all. It all depends on the implementation.
Comment linking /go-scheduler
on “Thread Pools in Nginx Boost Performance 9x (2015)”Submitted TCP is an underspecified two-node consensus algorithm as a story · 135 points
HN discussionThis is a good read on the Go scheduler. http://morsmachine.dk/go-scheduler
Comment linking /go-scheduler
on “Operating System Development in Rust”Submitted Causal Profiling for Go as a story · 81 points
HN discussionNot really an apples-to-apples comparison. It would have been nice to at least mention the possibility of goroutine starvation. Here's the best overview of goroutine scheduling I've come across so far: https://morsmachine.dk/go-scheduler
Comment linking /go-scheduler
on “Go routines vs. C threads”Submitted The Go netpoller (2013) as a story · 41 points
HN discussionSubmitted The Go Scheduler as a story · 10 points
HN discussionSubmitted The Go netpoller (2013) as a story · 5 points
HN discussionSubmitted TCP is an underspecified two-node consensus algorithm as a story · 4 points
HN discussionSubmitted Inside the Go runtime's netpoller as a story · 4 points
HN discussionSubmitted Causal Profiling for Go as a story · 3 points
HN discussionSubmitted Let's assess Kubernetes as a story · 2 points
HN discussionSubmitted The Go scheduler – Morsing's blog as a story · 2 points
HN discussionSubmitted The Go scheduler (2013) as a story · 2 points
HN discussionSubmitted A "Simpler" Look At Golang Scheduler as a story · 2 points
HN discussionSubmitted Go Scheduler as a story · 1 points
HN discussionSubmitted A Causal Profiling update as a story · 1 points
HN discussion
