Top all-time · #6630
Ionut Balosin
Personal blog · ionutbalosin.comprogrammingsystems
Ionut Balosin's personal blog at ionutbalosin.com covers programming and systems. Since 2019, 12 different Hacker News readers have linked it 14 times, most often “JVM Performance Comparison for JDK 17”. It is still writing: the last post was on 2026-06-02, and you can follow it by feed.
Too few sampled comments (2) to say how often HN recommends it.?
Why HN links it
HN readers link this blog for its JVM performance work, including a JVM garbage collectors benchmark report and a Java example showing how stack-trace creation makes exceptions slow.
Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- JVM Performance Comparison for JDK 172 people · 2 mentions · first linked 2023-03-20
What Hacker News says?
> Does anybody know the author of the article? You know this article is on his website, don't you? His name is the domain name. https://ionutbalosin.com/about-me/ > is/was he also a coder Seems unlikely anyone would be writing an article about Java GC, including having coded up benchmarks, without being able to code.
Comment linking /about-me/
on “JVM Garbage Collectors Benchmarks Report”Submitted JVM Garbage Collectors Benchmarks Report as a story · 119 points
HN discussion> Seems like a language design flaw that this is slow I think stack traces take up much of the time, including converting it [1]. Without them it could probably be a lot faster. Also see hashmash's post. But other than that, there is the logic issue, not using exceptions for normal flow control makes sense at least to me too independent of any performance questions. [1] For a Java example: https://ionutbalosin.com/2…
Comment linking /2018/06/getting-the-stack-trace-versus-throwing-an-exception-what-is-common-and-what-is-different/
on “Avoid exception throwing in performance-sensitive code”Submitted JVM Performance Comparison for JDK 21 as a story · 105 points
HN discussionSubmitted Deno: Help Us Raise $200k to Free JavaScript from Oracle as a story · 5 points
HN discussionSubmitted The Energy Consumption of JDK 21 as a story · 3 points
HN discussionSubmitted HotSpot JVM Performance Tuning Guidelines as a story · 3 points
HN discussionSubmitted JDK 26: G1 GC Throughput Improvements by 5-15% as a story · 2 points
HN discussionSubmitted JVM Performance Comparison for JDK 17 as a story · 2 points
HN discussionSubmitted Logging patterns and their performance impact as a story · 2 points
HN discussionSubmitted Analyzing JVM Energy Consumption for JDK 17: An Empirical Study as a story · 1 points
HN discussionSubmitted JVM Performance Comparison for JDK 17 as a story · 1 points
HN discussionSubmitted Do We Need an ORM? as a story · 1 points
HN discussionSubmitted JVM JIT Compilers Benchmarks Report 19.04 as a story · 1 points
HN discussion
