You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by zz...@apache.org on 2019/04/10 03:54:00 UTC
svn commit: r1857227 - in /cassandra/site:
publish/blog/2019/04/09/benchmarking_streaming.html
src/_posts/2019-04-09-benchmarking_streaming.markdown
Author: zznate
Date: Wed Apr 10 03:54:00 2019
New Revision: 1857227
URL: http://svn.apache.org/viewvc?rev=1857227&view=rev
Log:
Fix broken link to streaming post
Modified:
cassandra/site/publish/blog/2019/04/09/benchmarking_streaming.html
cassandra/site/src/_posts/2019-04-09-benchmarking_streaming.markdown
Modified: cassandra/site/publish/blog/2019/04/09/benchmarking_streaming.html
URL: http://svn.apache.org/viewvc/cassandra/site/publish/blog/2019/04/09/benchmarking_streaming.html?rev=1857227&r1=1857226&r2=1857227&view=diff
==============================================================================
--- cassandra/site/publish/blog/2019/04/09/benchmarking_streaming.html (original)
+++ cassandra/site/publish/blog/2019/04/09/benchmarking_streaming.html Wed Apr 10 03:54:00 2019
@@ -106,7 +106,7 @@
<p>As part of this replacement operation, the new Cassandra node streams data from the neighboring nodes that hold copies of the data belonging to this new nodeâs token range. Depending on the amount of data stored, this process can require substantial network bandwidth, taking some time to complete. The longer these types of operations take, the more we are exposing ourselves to loss of availability. Depending on your replication factor and consistency requirements, if another node fails during this replacement operation, ability will be impacted.</p>
<h2 id="increasing-availability">Increasing Availability</h2>
-<p>To minimize the failure window, we want to make these operations as fast as possible. The faster the new node completes streaming its data, the faster it can serve traffic, increasing the availability of the cluster. Towards this goal, Cassandra 4.0 saw the addition of <a href="https://en.wikipedia.org/wiki/Zero-copy">Zero Copy</a> streaming. For more details on Cassandraâs zero copy implementation, see this <a href="../../../2018/08/06/faster_streaming_in_cassandra.html">blog post</a> and <a href="https://issues.apache.org/jira/browse/CASSANDRA-14556">CASSANDRA-14556</a> for more information.</p>
+<p>To minimize the failure window, we want to make these operations as fast as possible. The faster the new node completes streaming its data, the faster it can serve traffic, increasing the availability of the cluster. Towards this goal, Cassandra 4.0 saw the addition of <a href="https://en.wikipedia.org/wiki/Zero-copy">Zero Copy</a> streaming. For more details on Cassandraâs zero copy implementation, see this <a href="../../../2018/08/07/faster_streaming_in_cassandra.html">blog post</a> and <a href="https://issues.apache.org/jira/browse/CASSANDRA-14556">CASSANDRA-14556</a> for more information.</p>
<h2 id="talking-numbers">Talking Numbers</h2>
<p>To quantify the results of these improvements, we, at Netflix, measured the performance impact of streaming in 4.0 vs 3.0, using our open source <a href="https://github.com/Netflix/ndbench">NDBench</a> benchmarking tool with the CassJavaDriverGeneric plugin. Though we knew there would be improvements, we were still amazed with the overall results of a <strong>five fold increase</strong> in streaming performance. The test setup and operations are all detailed below.</p>
Modified: cassandra/site/src/_posts/2019-04-09-benchmarking_streaming.markdown
URL: http://svn.apache.org/viewvc/cassandra/site/src/_posts/2019-04-09-benchmarking_streaming.markdown?rev=1857227&r1=1857226&r2=1857227&view=diff
==============================================================================
Binary files - no diff available.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org