1. X
  2. QuestDB
Log inSign up
QuestDB
2,494 posts
QuestDB profile banner
user avatar

QuestDB

@QuestDb
QuestDB (YC S20) is the fastest open source time series database. github.com/questdb/questdb
New York / London
questdb.com
Joined June 2019
266
Following
2,309
Followers
RepliesRepliesMediaMedia
  • user avatar
    QuestDB
    @QuestDb
    8h
    Cold partitions in #QuestDB land in object storage as Parquet. Point Apache Iceberg at them and Spark, Trino, DuckDB and PyIceberg can query your history in place. You write an Iceberg manifest over Parquet you already have and register incrementally new partitions.
    QuestDB banner titled 'Register it. Query anywhere.', tagged Interop · Apache Iceberg, with a pill reading 'metadata only, no copy, no rewrite.' On the right, three Parquet partition files dated 2026-08-11 through 2026-08-13 sit in a panel labeled 'object storage · parquet' marked UNCHANGED in green. A dashed arrow labeled REGISTER points down to a highlighted band reading 'Apache Iceberg table, metadata written, data untouched.' Below, under the label 'query from,' four chips read Spark, Trino, DuckDB and PyIceberg.
  • user avatar
    QuestDB
    @QuestDb
    Aug 12
    Your producer should not lose data to a network hiccup or a #QuestDB restart. Every QWP client in 10.0 buffers unacked writes, in memory by default, on disk if you give it a directory, and replays them when the server comes back. Publishing never blocks either way.
    QuestDB banner titled 'Buffer writes. Replay them.', tagged 10.0 · Store and forward, with a pill reading 'one key: sf_dir, memory or disk.' On the right, a connect string card shows http::addr=host:9000 with sf_dir=/var/qdb/sf highlighted, plus request_durable_ack=on and drain_orphans=on. Below it two cards compare the modes: sf_dir omitted gives Memory at 128 MiB, surviving rolling upgrades and brief partitions, suited to CLI, CI and serverless; sf_dir set to a path gives Disk at 10 GiB, surviving a crash or OOM kill and a host reboot, suited to long lived producers.
  • user avatar
    QuestDB
    @QuestDb
    Aug 10
    We ran TSBS against #QuestDB's new binary protocol and got 19M rows per second over a network, where line protocol gets 5.3M. The gain is the wire: 97 bytes per row against 347. ILP fills the link first. 48M rows/s on a single machine, 33M at a million series.
    Image
  • user avatar
    QuestDB
    @QuestDb
    Aug 7
    QWP, the new #QuestDB wire protocol, does egress as well as ingestion. Query results stream straight into Apache Arrow. 500 million rows in 2.3 seconds. 220 million rows per second. First batch after 32ms. 18.8 bytes per row on the wire. Two billion rows at 291M rows/sec.
    Image
  • user avatar
    QuestDB
    @QuestDb
    Aug 6
    We just shipped #QuestDB 10.0. QWP: one binary protocol for writes and Arrow reads, 3.6x faster ingestion, 220M rows/sec out. Live views in beta. Web Console notebooks, drivable by coding agents. Parquet tables with schema evolution. Enterprise 4.0 cold storage ships next.
    Image

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
Advertisement
Advertisement