My own benchmark refused to publish my numbers
I built a benchmark that decides by itself whether its numbers can be published. On the run I wanted to publish, it said no.
I built a benchmark that decides by itself whether its numbers can be published. On the run I wanted to publish, it said no.
In September 2026 I spent three days making a date parser faster. It already took less than a microsecond.
I made a Spring endpoint nine times faster this week. The way I did it is by skipping most of what Spring does to keep you safe.
The library worked. I spent two weeks rewriting large parts of it anyway, and broke compatibility on the way.
I like profilers. I also cannot use one where I need it most, which is in production, on the request that is slow right now.
1488153600. Is that seconds or milliseconds? You find out when the date lands in 1970 or in the year 49,000. APIs send timestamps like that since a number is fast to parse. I wanted to see how much of that is real, so I wrote a parser this weekend.