<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>thanatos_dem</author><text>7-8 seconds?  Something definitely sounds misconfigured.  I&amp;#x27;ve been running a 1.1.x cluster for quite a while and I&amp;#x27;ve never seen a single row transaction take that long.  And even the slowest queries took at most ~500ms, and that was with:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  - Replication factor increased to 5x (rather than the 3x default)
  - 8 indexes on the table being modified which also needed to be updated
  - Nodes spread across North America, incurring higher RTT latency between nodes
  - Relatively high contention on the data triggering client-side retries
  - HDD&amp;#x27;s as the storage medium (RockDB is optimized for SSDs)&lt;/code&gt;&lt;/pre&gt;</text><parent_chain><item><author>atombender</author><text>Looks very promising! We&amp;#x27;ve looked at Cockroach for a particular project, and we&amp;#x27;ve been concerned that performance wasn&amp;#x27;t good enough.&lt;p&gt;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 seconds, where Postgres would take just a few milliseconds.&lt;p&gt;The documentation recommends that you batch as many updates as possible, but obviously that doesn&amp;#x27;t work for low-latency applications like web frontends that need to be able to do small, fine-grained modifications.</text></item></parent_chain></comment><story><title>CockroachDB 2.0 Performance Makes Significant Strides</title><url>https://www.cockroachlabs.com/blog/2-dot-0-perf-strides/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jetrink</author><text>7-8 seconds seems extremely long. Human beings performing the raft consensus algorithm using paper and pencil over Skype wouldn&amp;#x27;t be much slower than that. Are you sure everything was working correctly?</text><parent_chain><item><author>atombender</author><text>Looks very promising! We&amp;#x27;ve looked at Cockroach for a particular project, and we&amp;#x27;ve been concerned that performance wasn&amp;#x27;t good enough.&lt;p&gt;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 seconds, where Postgres would take just a few milliseconds.&lt;p&gt;The documentation recommends that you batch as many updates as possible, but obviously that doesn&amp;#x27;t work for low-latency applications like web frontends that need to be able to do small, fine-grained modifications.</text></item></parent_chain></comment><story><title>CockroachDB 2.0 Performance Makes Significant Strides</title><url>https://www.cockroachlabs.com/blog/2-dot-0-perf-strides/</url></story>