logoalt Hacker News

BitPirate • today at 12:27 PM • 1 reply • view on HN

> Change JIT to be disabled by default (Jelte Fennema-Nio)

That was long overdue. The performance impact on perfectly fine tuned queries was horrendous.

It's also disabled by most OSM apps that make heavy use of PostGIS for exactly that reason.

Maybe it wouldn't be that bad if a copy-and-patch kind of JIT would be used?


Replies

Sesse__ • today at 12:49 PM

Copy-and-patch is going to generate worse code than the LLVM-based JIT, all things being equal. You'll get shorter compile times, but in my experience, that's only really a part of the JIT's problems. TBH it's a bit sad that they turned on the JIT in the current state to begin with; it clearly wasn't ready, and perhaps needed a couple more rounds with the design.

Out of curiosity, are there any copy-and-patch JITs that are clear-cut successes? (Python's JIT is the most high-profile case, and it's definitely not one.)