←
ObsessionDB113 posts
ObsessionDB avatar

ObsessionDB

@ObsessionDB

The best ClickHouse® database performance per dollar | obsessiondb.com

◷ Joined March 2026▧ 18 Photos and videos
ObsessionDB avatar
ObsessionDB@ObsessionDB·Oct 20

Agents are hungry for data, and we are here to feed that appetite. Meet ObsessionDB, the fastest and most scalable data warehouse for AI.

Today we are launching @ObsessionDB, the realtime data warehouse for agents. Your agents are hungry for data. Feeding them is getting expensive. Your data warehouse wasn't built (or priced) for that. We learned this the hard way. We scaled our last company to petabytes on ClickHouse and watched the infra bill go vertical. So we built @ObsessionDB . The ClickHouse engine, rebuilt with compute and storage separated, so your infra scales with your agents instead of your bill. 100x faster and 20x cheaper than Snowflake and Databricks. Already live, processing trillions of rows a day. Agents are just getting started...

0:58
marcmacmac avatar
⟳ ObsessionDB retweeted
marcmacmac@marcmacmac·Nov 15

infect your customers! it's 50% obsessiondb, the other 50% is enable your customers to become obsessed with their performance, too.

Post attachment
Rafa Aviles avatar
⟳ ObsessionDB retweeted
Rafa Aviles@avilesrafa·Nov 13

If you self-host ClickHouse® or overpay for a managed service, this is for you. Cheap storage, auto-scaling and scale-to-zero, no more Keeper, no more ReplicatedMergeTree, and the fastest ClickHouse engine out there. All of this in your own Cloud at @ObsessionDB

0:49
marcmacmac avatar
⟳ ObsessionDB retweeted
marcmacmac@marcmacmac·Nov 9

helped a friend - not our customer, yet - save some additional nodes at his provider, just by merging down their massive backlog. they thought their latency went up because "we have more data and usage". p50 back to <20ms. sometimes the problem isn't that you need more resources. it's that selling you more is in the provider's own interest.

Post attachmentPost attachment
marcmacmac avatar
⟳ ObsessionDB retweeted
marcmacmac@marcmacmac·Nov 5

we're shutting down more than 1/3 of a customer's nodes. 4 digits saved, still 1.5-2.2x better performance. clickhouse's upstream default for merge_tree_min_bytes_per_task_for_remote_reading is 2MiB, try +16MiB.

Post attachment
ObsessionDB avatar
ObsessionDB@ObsessionDB·Nov 3

RT @marcmacmac: here's a tough one: HRW distributed network cache. two contradicting values: part size (smaller parts for more performance)…

marcmacmac avatar
⟳ ObsessionDB retweeted
marcmacmac@marcmacmac·Nov 1

got alerted for an instance going crazy last night. turns out a potential customer ran a benchmark. they moved on to sign this morning.

Post attachment
ObsessionDB avatar
ObsessionDB@ObsessionDB·Oct 30

Ummm, no big deal…

cross-region data availabilty between us-west-2 <-> us-east-1a. we serve real-time apis on large data sets around the globe close to physics.

Post attachment
marcmacmac avatar
⟳ ObsessionDB retweeted
marcmacmac@marcmacmac·Oct 30

cross-region data availabilty between us-west-2 <-> us-east-1a. we serve real-time apis on large data sets around the globe close to physics.

Post attachment
marcmacmac avatar
⟳ ObsessionDB retweeted
marcmacmac@marcmacmac·Oct 29

impact of metadata's proximity to your query engine. starts with the time you lose in sequential querying, ends with the max capacity of the cluster.

Post attachment
Alvaro avatar
⟳ ObsessionDB retweeted
Alvaro@alvaro__data·Oct 22

ObsessionDB now runs in your own AWS or GCP account. Your data stays in your bucket and nothing on our side connects in. We run upgrades, scaling and on-call. Cut the link to our control plane and your queries keep running.

0:23
Rafa Aviles avatar
⟳ ObsessionDB retweeted
Rafa Aviles@avilesrafa·Oct 6

Unpopular opinion: your data warehouse/platform should not make money from your waste. Today, most of them do. Consumption pricing means your vendor earns more when your queries or schema are suck. Some of them charge crazy multiples on the underlying infra. That is not a partnership; it feels like they are extracting from you. Data warehouses and data platforms should be more aligned with customers: 1. Infra at cost. You see the real cloud bill, line by line. 2. One platform fee. No overages. No markup. 3. Run it in your cloud, on your hardware, or go managed. No difference in the price. If we save you money, we should win too. If your bill goes up because you burned more compute, we don't extract extra margins. The old model doesn't make any sense to me. Is this naive?

Rafa Aviles avatar
⟳ ObsessionDB retweeted
Rafa Aviles@avilesrafa·Sep 19

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.

Post attachment