From 9a80f803c2ec9a4a74cb8a99293dc81ef3dc183d Mon Sep 17 00:00:00 2001 From: Ariel Weisberg Date: Tue, 14 Feb 2017 15:09:20 -0500 Subject: [PATCH] Remove non-ascii characters from cassandra.yaml introduced by CASSANDRA-13090 patch by Ariel Weisberg; reviewed by Jason Brown for CASSANDRA-13219 --- conf/cassandra.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml index ddb7927bc1..41c1fb19d9 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