Add ObsessionDB - #2083
Add ObsessionDB#2083marcmacmac wants to merge 1 commit into
Conversation
|
I've logged in to ObsessionDB, but can't find a button to create services with these sizes. Could you please share screenshots or detailed steps? |
|
Hey @alexey-milovidov, thanks for checking. It's available for our enterprise customers only. I added four clusters with two nodes each for the 8, 16, 32 and 64GB tiers to your account. Here's how you can access it On the top left select your service In the left navigation select "Connect" and there you'll find your connection details. Let me know if you have any questions with it. |
|
I'll check it. But the results should be reproducible by a user "from the street" to publish. |
|
That's fair. I appreciate your effort anyhow. Our public self-service is around the corner. So I'd ping you once everyone can verify it "from the street". |

Add ObsessionDB
ObsessionDB is a ClickHouse-based database with separated compute and storage: data on
object storage, a metadata layer and a distributed NVMe cache shared across the
compute nodes. The table engine is our own implementation, built against the open-source
SharedMergeTreeAPI.22 results: seven service sizes (8, 16, 32, 64, 128, 256, 336 GiB) at 1, 2 and 3 nodes, plus
one single-node dev instance.
Method
The entry is deliberately a copy of
clickhouse-cloud, because the two systems are operated thesame way and we did not want any ambiguity in the comparison:
clickhouse-cloudrun.shqueries.sqlcreate.sqlbenchmark.shurlCluster('cluster', ...)instead ofurlCluster('default', ...)—clusteris the cluster name on an ObsessionDB serviceWe picked up #2046, the
urlClustersource and theEXPECTED_ROWSguard. The row-count guard is a good addition and we kept it.