Viewing profile — hnkimb3558
hnkimb3558
HN member- Joined
- Wed, Feb 17, 2016, 7:58 PM UTC
- HN karma
- 57
- Public activity
- 13 items
- HN profile
- View on Hacker News ↗
About hnkimb3558
Recent public activity
-
comment
Comment #40285039
What's next after optimizing for Snowflake costs?
-
comment
Comment #16757951
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 wri…
-
comment
Comment #16756427
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 transactio…
-
comment
Comment #15468357
I think the algorithm is whoever comes up with the most egregious and sticky name wins.
-
comment
Comment #15461544
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 Coc…
-
comment
Comment #13447618
[Post author here] I second the sentiment that you should publish. This would be invaluable.
-
comment
Comment #13447599
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 …
-
comment
Comment #13439899
(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…
-
comment
Comment #11637920
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 64…
-
comment
Comment #11637011
(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 …
-
comment
Comment #11130154
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. Cockroach…
-
comment
Comment #11126187
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 so…
-
comment
Comment #11122402
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 pr…