"For instance, on a cluster of five m3.large nodes, an even mixture of processes performing single-row inserts and selects over a few hundred rows pushed ~40 inserts and ~20 reads per second (steady-state)." Wow, that's...not fast.
CockroachDB beta-20161013
71–80 of 213 posts
Re: CockroachDB beta-20161013
#72Could the name actually slow the project's momentum? I only recently read some cool things about CDB and wondered if I could have been subconsciously skipping articles about it for deep seeded reasons like http://bbc.com/future/story/20140918-the-reality-about-roach... Of course anything good may eventually rise to success on its merits, but in case I'm not the only one with a subconscious aversion maybe the info bel…
Agree 100%, ditto for suggested alternate name. I'd been doing the same for Rust. It's not a rational reason, sure, but I have to sell adoption to a broader userbase that cares about more that the technical merits. I don't want to have to make the case for why someone's system needs rust and cockroaches.
Re: CockroachDB beta-20161013
#73Could the name actually slow the project's momentum? I only recently read some cool things about CDB and wondered if I could have been subconsciously skipping articles about it for deep seeded reasons like http://bbc.com/future/story/20140918-the-reality-about-roach... Of course anything good may eventually rise to success on its merits, but in case I'm not the only one with a subconscious aversion maybe the info bel…
Re: CockroachDB beta-20161013
#74Could the name actually slow the project's momentum? I only recently read some cool things about CDB and wondered if I could have been subconsciously skipping articles about it for deep seeded reasons like http://bbc.com/future/story/20140918-the-reality-about-roach... Of course anything good may eventually rise to success on its merits, but in case I'm not the only one with a subconscious aversion maybe the info bel…
I agree completely. I love reading about databases, but apparently have been skipping reading about CockroachDB for that same reason subconsciously. I took a deep dive the other day and was amazed that I've seen the name dozens of times and have never bothered to ask what was special about it. It really is a fascinating database.
Re: CockroachDB beta-20161013
#75Earlier quoted context omitted.
Ah yes, let's not forget the solid branding behind some of Adobe's work: https://pig.apache.org/ https://hive.apache.org/ (Look at the anguish in this creature's face) http://hadoop.apache.org/
Wait, is hive supposed to look like some elephant-bee hybrid?
Re: CockroachDB beta-20161013
#76Wow. Probably fundraising and getting out front of googles new consumer spanner service. I just started experimenting w/ cockroachdb and it sounds/seems great. They def are campaigning hard, landing a Jepsen test and a lot of posts/articles last couple. I am pulling for them over G on principle. I infer they know people at Stripe where the Rethink team & Aphyr are so hopefully they can learn from them and build an aw…
Just as a headsup, I left Stripe in late 2015 to run Jepsen as an independent consultancy.
Re: CockroachDB beta-20161013
#77"For instance, on a cluster of five m3.large nodes, an even mixture of processes performing single-row inserts and selects over a few hundred rows pushed ~40 inserts and ~20 reads per second (steady-state)." Wow, that's...not fast.
I wonder how the clock skew bounds affect performance. Would a more accurate clock increase throughput?
Re: CockroachDB beta-20161013
#78Earlier quoted context omitted.
I'm not a native English speaker and have troubles pronouncing "cockroach". In my view the naming is rather unfortunate.
Do you find it easier to pronounce "postgres"?
If you're postgres, it doesn't really matter because you're already there.
Re: CockroachDB beta-20161013
#79"For instance, on a cluster of five m3.large nodes, an even mixture of processes performing single-row inserts and selects over a few hundred rows pushed ~40 inserts and ~20 reads per second (steady-state)." Wow, that's...not fast.
(Cockroach Labs CTO here) Jepsen is essentially a worst-case stress test for a consistent database: all the transactions conflict with each other. CockroachDB's optimistic concurrency control performs worse with this kind of workload than the pessimistic (lock-based) concurrency control seen in most non-distributed databases. But this high-contention scenario is not the norm for most databases. Most transactions don'…
Re: CockroachDB beta-20161013
#80CDB is a really cool db for the time I've been playing with it (just a few months I think). That said, I'd really appreciate if they'd launch a hosted DBaaS. By that I mean, more in line with dynamodb or documentdb instead of say MySQL on AWS for example. I know it's on their timeline, but dbs generally get selected during the start of the projects and unless absolutely necessary, companies don't want to change dbs.