TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Why we changed our approach to memory mapping at QuestDB (YC S20)

1 pointsby bluestreakover 4 years ago

1 comment

bluestreakover 4 years ago
Hi HN,<p>Author here. QuestDB is a fast SQL open source database for time series. About a month ago we launched on HackerNews [1].<p>Today, I am excited to announce QuestDB 5.0.3 [2]. This new release includes our changes in memory mapping strategy, giving us better performance, as well as some major changes to the Postgres wire protocol support.<p>In this blog post, we explain our journey to improve QuestDB&#x27;s performance, especially regarding memory management. Relying as much as possible on the kernel and avoiding extra layers turned out to be very successful.<p>Thanks<p>Vlad<p>[1] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=23975807" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=23975807</a><p>[2] <a href="https:&#x2F;&#x2F;questdb.io&#x2F;getstarted&#x2F;" rel="nofollow">https:&#x2F;&#x2F;questdb.io&#x2F;getstarted&#x2F;</a>