Earlier quoted context omitted.
7-8 seconds seems extremely long. Human beings performing the raft consensus algorithm using paper and pencil over Skype wouldn't be much slower than that. Are you sure everything was working correctly?
I don't know about you, but it would take me a lot longer than 7 seconds to perform the raft consensus algorithm with paper and pencil.
CockroachDB 2.0 Performance Makes Significant Strides
131–140 of 187 posts
Re: CockroachDB 2.0 Performance Makes Significant Strides
#132Earlier quoted context omitted.
We have a collaborative, Google Docs-like application that currently issues a write every time someone types into a text field. Now, clearly it's suboptimal and something that should be optimized to batch the updates, but on the other hand, with Postgres we've had zero incentive to make such an optimization, because it's able to handle thousands of writes per node in real time with no queuing happening on the client.…
Lordy, relational databases are not the way to go for that problem... With a single shared resource (document), you're going to be encountering write conflicts left and right. Have you explored implementing a CRDT based solution like WOOT instead?
CRDTs could be a solution, but from what I gather they require too much context information to be viable for a text editing application. Our app currently uses something similar to OT.
Re: CockroachDB 2.0 Performance Makes Significant Strides
#133Looks very promising! We've looked at Cockroach for a particular project, and we've been concerned that performance wasn't good enough. Cockroach performance seems to scale linearly, but single-connection performance, especially for small transactions, seems rather dismal. Some casual stress testing against a 3-node cluster on Kubernetes showed that small transactions modifying a single row could take as much as 7-8…
" small transactions modifying a single row could take as much as 7-8 seconds" That's surprising. I wasn't expecting CockroachDB to be really fast, given the constraints they work within. But that sounds more like a bug or config error. Unless perhaps you mean a really high number of processes trying to update the same row at the same time? Like a global counter or something?
Re: CockroachDB 2.0 Performance Makes Significant Strides
#134Looks very promising! We've looked at Cockroach for a particular project, and we've been concerned that performance wasn't good enough. Cockroach performance seems to scale linearly, but single-connection performance, especially for small transactions, seems rather dismal. Some casual stress testing against a 3-node cluster on Kubernetes showed that small transactions modifying a single row could take as much as 7-8…
Did you use the 2.0 beta version or the latest stable release? They improved performance a lot in the 2.0 beta released this month.
Re: CockroachDB 2.0 Performance Makes Significant Strides
#135Earlier quoted context omitted.
Why write conflicts? Contention, sure, but contention isn't an issue until you have literal tons of it.
From OP's description > issues a write every time someone types into a text field With more than a handful of people, this is getting into conflict territory pretty rapidly, especially if the document is structured as a single row (hopefully it's more granular than that). Time for some back of the envelope maths: Assuming that an average person types at around 200 words per minute (number pulled from https://www.live…
Re: CockroachDB 2.0 Performance Makes Significant Strides
#136I dont like when companies are not transparent about the pricing of their product. If you have a price page, show the price, so that Í can decide if this is relevant for me or not ...
Re: CockroachDB 2.0 Performance Makes Significant Strides
#137How is this meaningful without detailed setup description? http://www.tpc.org/tpcc/results/tpcc_results.asp?print=false... Looking at this list of results one wonders what those results actually mean?
I think you can still drive some insights. I clicked on the TPC-C results you shared and read their executive summaries. The Oracle on SPARC cluster (at the top, 2010) performs 30.2M qualified tx/min vs the 16K tx/min in this blog post. The Oracle cluster also costs $30M, which is clearly higher than the Cockroach cluster's cost. That said, the TPC-C benchmark is new to me. Happy to update this comment if I'm misread…
Re: CockroachDB 2.0 Performance Makes Significant Strides
#138Earlier quoted context omitted.
I don't know about you, but it would take me a lot longer than 7 seconds to perform the raft consensus algorithm with paper and pencil.
Who are you to judge? Did you win the Putnam or something?
Re: CockroachDB 2.0 Performance Makes Significant Strides
#139Project idea: globally hosted / managed CockroachDB that lets developers quickly start building small apps cheaply or free using this database. This database has the potential to dethrone Spanner in a major way.
Re: CockroachDB 2.0 Performance Makes Significant Strides
#140Earlier quoted context omitted.
Who are you to judge? Did you win the Putnam or something?
I think people are generally allowed to judge themselves without industry credentials...