TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

I wrote a new JIT compiler for PostgreSQL

290 点作者 mattashii大约 1 年前

5 条评论

weliveindetail大约 1 年前
&gt; There is one way to make the LLVM JIT compiler more usable, but I fear it’s going to take years to be implemented: being able to cache and reuse compiled queries.<p>Actually, it&#x27;s implemented in LLVM for years :) <a href="https:&#x2F;&#x2F;github.com&#x2F;llvm&#x2F;llvm-project&#x2F;commit&#x2F;a98546ebcd2a692e0634c5b1a7e77471316ab6e0">https:&#x2F;&#x2F;github.com&#x2F;llvm&#x2F;llvm-project&#x2F;commit&#x2F;a98546ebcd2a692e...</a>
评论 #39744716 未加载
评论 #39745796 未加载
pinaraf大约 1 年前
Author here. Thanks for submitting my article on hackernews. I&#x27;ll do my best to answer any question.
评论 #39746397 未加载
评论 #39755568 未加载
评论 #39753342 未加载
评论 #39744106 未加载
评论 #39743964 未加载
评论 #39744104 未加载
评论 #39744123 未加载
adzm大约 1 年前
I&#x27;m still surprised there isn&#x27;t a query&#x2F;plan cache for PostgreSQL. I could easily see these two approaches working in harmony once it does, as frequent queries could end up being cached and more aggressively optimized with a cache to offset the compilation cost. Of course that adds a whole new layer of complexity and trouble.
评论 #39744438 未加载
评论 #39744324 未加载
评论 #39745232 未加载
miohtama大约 1 年前
Back in 386 era, there was a concept of self-modifying code (assembly). A similar like stencils presented here, but because code was a singleton, rarely a copy was made.<p>E.g. Doom on DOS used this optimisation techique, because otherwise you could not cram out enough performance from tight rendering loops on old CPUs.
HackerThemAll大约 1 年前
Interesting work, please continue it. Great times ahead. Thanks!