cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aweisb...@apache.org
Subject [01/10] cassandra git commit: Remove non-ascii characters from cassandra.yaml introduced by CASSANDRA-13090
Date Tue, 14 Feb 2017 21:32:21 GMT
Repository: cassandra
Updated Branches:
  refs/heads/cassandra-2.2 5725e2c42 -> 9a80f803c
  refs/heads/cassandra-3.0 3d01e9061 -> 82943d6aa
  refs/heads/cassandra-3.11 702ec088f -> 23a1dee45
  refs/heads/trunk 3f3db2d40 -> 48bfc8e8d


Remove non-ascii characters from cassandra.yaml introduced by CASSANDRA-13090

patch by Ariel Weisberg; reviewed by Jason Brown for CASSANDRA-13219


Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/9a80f803
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/9a80f803
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/9a80f803

Branch: refs/heads/cassandra-2.2
Commit: 9a80f803c2ec9a4a74cb8a99293dc81ef3dc183d
Parents: 5725e2c
Author: Ariel Weisberg <aweisberg@apple.com>
Authored: Tue Feb 14 15:09:20 2017 -0500
Committer: Ariel Weisberg <aweisberg@apple.com>
Committed: Tue Feb 14 15:09:20 2017 -0500

----------------------------------------------------------------------
 conf/cassandra.yaml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cassandra/blob/9a80f803/conf/cassandra.yaml
----------------------------------------------------------------------
diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml
index ddb7927..41c1fb1 100644
--- a/conf/cassandra.yaml
+++ b/conf/cassandra.yaml
@@ -892,10 +892,10 @@ windows_timer_interval: 1
 
 # Coalescing Strategies #
 # Coalescing multiples messages turns out to significantly boost message processing throughput
(think doubling or more).
-# On bare metal, the floor for packet processing throughput is high enough that many applications
won’t notice, but in
+# On bare metal, the floor for packet processing throughput is high enough that many applications
won't notice, but in
 # virtualized environments, the point at which an application can be bound by network packet
processing can be
-# surprisingly low compared to the throughput of task processing that is possible inside
a VM. It’s not that bare metal
-# doesn’t benefit from coalescing messages, it’s that the number of packets a bare metal
network interface can process
+# surprisingly low compared to the throughput of task processing that is possible inside
a VM. It's not that bare metal
+# doesn't benefit from coalescing messages, it's that the number of packets a bare metal
network interface can process
 # is sufficient for many applications such that no load starvation is experienced even without
coalescing.
 # There are other benefits to coalescing network messages that are harder to isolate with
a simple metric like messages
 # per second. By coalescing multiple tasks together, a network thread can process multiple
messages for the cost of one


Mime
View raw message