Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderErlang has a parameter called initial_heap_size. Each new actor-process in Erlang gets its own isolated heap, for which it does its own garbage-collection on its own execution thread. This initial_heap_size parameter determines how large each newly-spawned actor’s heap will be. Why would you tune it? Because, if you set it high enough, then for all your short-lived actors, memory allocation will become a no-op (= bump allocation), and the actor will never experience enough memory-pressure to trigger a…
This reminds me of a demo a friend once gave me on a Symbolics Lisp Machine. He turned the garbage collector off, then ran a program that allocated memory like mad. After a while, a message popped up saying something like "you are about to run out of memory. Activate GC?" He declined, and the program continued running. After a bit more time, another message popped up saying "you are about to run out of memory, and if you don't…
The previous discussion is https://news.ycombinator.com/item?id=14233542
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 738
- Total comments
- 357
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2017-04-30 | The Ultimate in Garbage Collection (1995)First breakout | tjalfi | 144 | 45 |
| 2018-02-28 | Intentional memory leaks | throwaway2048 | 91 | 33 |
| 2020-02-22 | Does memory leak? (1995)Best thread · Latest 20+ point return | rot25 | 503 | 279 |