News for hackers. Stuff that matters.
Re:A 40-line fix eliminated a 400x performance gap by jabwd on Tuesday January 13, 2026 @10:09PM (#46611831)
I might be very wrong in every way but, string parsing and or manipulating and memoiziation... sound like a super strange combo? For the first you know you're already doing expensive allocations, but the 2nd is also not a pattern I really see apart from in JS codebases. Could you provide more context on how this actually bit you in the behind? memoizing strings seems like a complicated and error prone "welp it feels better now" territory in my mind so I'm genuinely curious.
Re:A 40-line fix eliminated a 400x performance gap by shermantanktop on Tuesday January 13, 2026 @11:21PM (#46612305)
In Java it can be a bad toString() implementation hiding behind a + used for string assembly.

Or another great one: new instances of ObjectMapper created inside a method for a single call and then thrown away.

Re:A 40-line fix eliminated a 400x performance gap by shermantanktop on Wednesday January 14, 2026 @12:06AM (#46612542)
To be clear this is often sloppy code that shouldn’t have been written. But in a legacy codebase this stuff can easily happen.
Re:A 40-line fix eliminated a 400x performance gap by MengerSponge on Wednesday January 14, 2026 @10:46PM (#46627775)
A huge chunk of a "legacy codebase" is "sloppy code that shouldn’t have been written"

Unless you're inheriting code written by Bill Atkinson or something.

Re:A 40-line fix eliminated a 400x performance gap by tyingq on Tuesday January 13, 2026 @10:14PM (#46611864)
> but the 2nd is also not a pattern I really see apart from in JS codebases.

If you're referring to "one-line logger calls that trigger expensive serialization", it's also common in java.