cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-14556) Optimize streaming path in Cassandra
Date Fri, 13 Jul 2018 22:21:00 GMT


ASF GitHub Bot commented on CASSANDRA-14556:

Github user aweisberg commented on a diff in the pull request:
    --- Diff: conf/cassandra.yaml ---
    @@ -784,6 +784,15 @@ compaction_throughput_mb_per_sec: 16
     # between the sstables, reducing page cache churn and keeping hot rows hot
     sstable_preemptive_open_interval_in_mb: 50
    +# When enabled, permits Cassandra to zero copy eligible SSTables between
    --- End diff --
    Worth documenting this optimization relies on having sstables that are wholly contained
in the range being streamed and that configurations like size tiered without 6696 won't benefit,
and would in fact spend time reading indexes checking to see if the optimization applies?
Leveled should always benefit from this optimization.

> Optimize streaming path in Cassandra
> ------------------------------------
>                 Key: CASSANDRA-14556
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Streaming and Messaging
>            Reporter: Dinesh Joshi
>            Assignee: Dinesh Joshi
>            Priority: Major
>              Labels: Performance
>             Fix For: 4.x
> During streaming, Cassandra reifies the sstables into objects. This creates unnecessary
garbage and slows down the whole streaming process as some sstables can be transferred as
a whole file rather than individual partitions. The objective of the ticket is to detect when
a whole sstable can be transferred and skip the object reification. We can also use a zero-copy
path to avoid bringing data into user-space on both sending and receiving side.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message