The best ClickHouse® database performance per dollar | obsessiondb.com
- Tweets 96
- Following 2
- Followers 34
- Likes 26
ObsessionDB retweeted
We just added Jev support to ObsessionDB/ClickHouse.
The interesting part isn’t just “LLM in SQL”, it’s that Jev is fast enough to make semantic queries feel like part of the database workflow.
You can analyze AI agent sessions on the go!
aiFilter(session, 'was the user frustrated, map('model','jev-1.13.0'))
or score frustration, success, intent, exposed credentials, etc.
At write time: turn meaning into columns.
At read time: ask new questions you never instrumented.
~50 rows/request, ~300ms in our current setup.
Feels like a new primitive for AI product telemetry.
3
3
9
231
ObsessionDB retweeted
Just waiting for the PR getting merged to finally see ObsessionDB on benchmark.clickhouse.com. Spoiler: It's fast
4
4
84
56 TB of data (203 billion rows) on ObsessionDB, with live ingestion, and we managed to run 100% of the queries in under one second.
Slowest: 977 ms.
Three things made that possible 🧵
1
4
6
80
4/ Third, a cache shared across servers.
With storage and compute decoupled, each server caches only what it has read/ingest. More servers means more cold caches, and each miss is a 10 to 50 ms trip to S3.
Our cache mesh lets any server read any other server's NVMe in ~0.1 ms.
1
10
Locality-aware routing: sending each query to the servers that already hold its data took the same query from 1.0 s to 0.5 s on the same six servers.
Result on 56 TB: p99 703 ms, max 977 ms.
Full write-up: obsessiondb.com/blog/subseco…
7
ObsessionDB retweeted
Three replicas of a ClickHouse® table mean three full copies of the same data.
You are paying your storage bill three times and calling it durability.
The replication tax nobody names:
1
3
7
159
Getting data from another team, vendor or customer usually means an export, a replica, or a sync job that drifts. Datashares are now in beta on ObsessionDB: one customer exposes databases or tables, another queries them directly. No copy anywhere.
1
3
60
Why no copy? Most databases are shared-nothing: each node owns its slice of data, so sharing means exporting it. ObsessionDB is shared-storage: data lives exactly once as immutable objects and compute is stateless, so another customer's compute can read the very same objects.
1
8
In beta for every customer. Reach out if you want to test it.
Full entry: obsessiondb.com/changelog/da…
Previously in the changelog:
Jul 3, 2026: a backfill is usually one enormous query you fire and hope finishes. Every ObsessionDB service now has a Jobs section for long-running batch SQL: backfills, big dataset loads, heavy maintenance. It runs task by task, and you can step in at any point.
4
Jul 3, 2026: a backfill is usually one enormous query you fire and hope finishes. Every ObsessionDB service now has a Jobs section for long-running batch SQL: backfills, big dataset loads, heavy maintenance. It runs task by task, and you can step in at any point.
1
2
51
Open a job and watch it run: percent complete, tasks done vs running vs waiting, data read and written, current throughput. Down to the SQL each task ran and how many rows it moved.
1
13
You stay in control. Pause and in-flight tasks finish cleanly; resume when ready, or cancel outright. A failed task can be retried on its own, and every attempt keeps its exact error.
Full entry: obsessiondb.com/changelog/jo…
Previously in the changelog:
Jun 23, 2026: most monitoring tells you something's broken after you go looking. We wanted the cluster to tell us first.
Alerts is live in ObsessionDB: write a SQL query, set a threshold, and we watch it for you.
13
Jun 23, 2026: most monitoring tells you something's broken after you go looking. We wanted the cluster to tell us first.
Alerts is live in ObsessionDB: write a SQL query, set a threshold, and we watch it for you.
1
2
67
Firings route to Slack or any webhook (PagerDuty and Opsgenie coming).
Every alert reads as firing, acked, or resolved, with the full incident: metric chart, the rule behind it, and a history timeline.
Plus a paste-ready prompt to hand straight to an AI agent.
1
18
No setup to start. New Alerts tab on every service.
See it: obsessiondb.com/changelog/al…
How are you alerting on your ClickHouse® clusters today?
Previously in the changelog:
Week of Jun 22, 2026: nobody wants another password for a database console. Now you don't need one. Type your email, we send a 6-digit code, you're in. New email? Account created on the spot. Existing one? Signed in.
1
29