hnkimb3558

4 ms·

1.
by hnkimb3558 2y ago
What's next after optimizing for Snowflake costs?
2.
by hnkimb3558 9y ago
I just read up on that issue. We will follow up with updated measurements with CRDB 2.0. The big reason for the discrepancies you measured is likely the fact that each sqlbench write transaction is doing six consecutive consensus writes (in
3.
by hnkimb3558 9y ago
Performance is a very tricky thing to measure in a database. CockroachDB's performance is certainly affected by its consistency model. In particular, CockroachDB handles transactions using serializable isolation, and writes using conse
4.
by hnkimb3558 9y ago
I think the algorithm is whoever comes up with the most egregious and sticky name wins.
5.
by hnkimb3558 9y ago
Pete chose the name GIMP (we were mulling calling it "XIMP", for X11 Image Manipulation Program, but Pulp Fiction had recently been released, so...). I (spencer) chose the name CockroachDB. I guess we have questionable tastes in O
6.
by hnkimb3558 10y ago
[Post author here] I second the sentiment that you should publish. This would be invaluable.
7.
by hnkimb3558 10y ago
Post author here. First off, I really appreciated your frank blog post on the RethinkDB post mortem. The distillation of years of experience is incredibly valuable for us, and I'm sure for many others. I agree that the database market
8.
by hnkimb3558 10y ago
(Post author here) I'm not incredibly familiar with the ins and outs of MongoDB Inc's business model, but I agree with your assessment. They certainly seem to have embraced both of the OSS business models I described in the post a
9.
by hnkimb3558 10y ago
I'm not really sure which strategy would benchmark best between 64K chunks, 1M chunks, or even 8M chunks. I think this requires some experimentation. Pushing them all through as 64K chunks has a lot of overhead, and you'd reap the
10.
by hnkimb3558 10y ago
(employee/founder here) Anything under 64K is perfectly reasonable to store in a CockroachDB column. Between 64K and maybe 1M is trending towards trouble. Values greater than this are going to go through CockroachDB like a goat through
11.
by hnkimb3558 11y ago
Cockroach enforces this guarantee on a per-key basis as opposed to for the entire node. If a key has been read at time t, it may only be subsequently written at time > t. CockroachDB accomplishes this using a timestamp cache at the leade
12.
by hnkimb3558 11y ago
CockroachDB's time api is based on the Hybrid Logical Clocks paper. We credit it on our design doc ( https://github.com/cockroachdb/cockroach/blob/master/docs/de... ) and in the source code. This
13.
by hnkimb3558 11y ago
These are conservative upper bounds and are meant to encompass long tail offsets. You can usually get NTP down to < 10ms offsets, but if you rely on that, you'll likely run into problems which end up violating your database guarante