Top all-time · #17831
tkowal
Personal blog · tkowal.wordpress.comprogramming
tkowal is a personal blog at tkowal.wordpress.com about programming. Since 2015, 4 different Hacker News readers have linked it 11 times, most often “The unintuitive latency over throughput problem”. The last post was in 2016, but the archive is still widely read.
Too few sampled comments (1) to say how often HN recommends it.?
Why HN links it
The one comment is a general discussion of BEAM's pre-emptive processes for hardware and higher-level tasks, compared with cooperative multitasking in Lua, Node, Python and Go. It does not mention the linked post.
Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Not only programming
Most-linked posts?
- The unintuitive latency over throughput problem2 people · 3 mentions · first linked 2015-08-04
- Observing Erlang/Elixir production releses2 people · 2 mentions · first linked 2016-04-25
- The principle of immediate feedback2 people · 2 mentions · first linked 2015-10-22
What Hacker News says?
The ability to utilize the BEAM's fully pre-emptive processes makes it great for programming hardware tasks and higher level tasks in the same environment. Compared to other languages like Lua, Node, Python, or even Go which all use various forms of cooperative multi-tasking or async-io. In these systems you have to be careful not to block other critical tasks. That's a pain but not the end of the world. However, fo…
Comment linking /2016/04/23/observer-in-erlangelixir-release/
on “Nerves – Craft and deploy bulletproof embedded software in Elixir”Submitted The unintuitive latency over throughput problem as a story · 3 points
HN discussionShort answer: scheduler. Long answer: web applications have usually tons of independent request. Each request does its own thing, might never communicate with other requests, touches the DB and returns. You have two choices in such scenarios. You can either maximise throughput or minimise latency. BEAM's scheduler choses the latter which is usually what you want for web. More detailed discussion: https://tkowal.word…
Comment linking /2015/01/27/the-unintuitive-latency-over-throughput-problem/
on “Things I like about Gleam's Syntax”Submitted Summary of Elixir Conf EU 2016 as a story · 3 points
HN discussionSubmitted Building docker images for Elixir applications as a story · 3 points
HN discussionSubmitted Observing Erlang/Elixir production releses as a story · 2 points
HN discussionSubmitted What problems does Elm solve? as a story · 2 points
HN discussionSubmitted Failing fast and slow in Erlang and Elixir as a story · 2 points
HN discussionSubmitted The principle of immediate feedback as a story · 2 points
HN discussionSubmitted The Principle of Immediate Feedback as a story · 1 points
HN discussionSubmitted The unintuitive latency over throughput problem as a story · 1 points
HN discussion