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 Mon, 23 Jul 2018 20:12:00 GMT


ASF GitHub Bot commented on CASSANDRA-14556:

Github user iamaleksey commented on a diff in the pull request:
    --- Diff: src/java/org/apache/cassandra/db/streaming/ ---
    @@ -0,0 +1,97 @@
    + * Licensed to the Apache Software Foundation (ASF) under one
    + * or more contributor license agreements.  See the NOTICE file
    + * distributed with this work for additional information
    + * regarding copyright ownership.  The ASF licenses this file
    + * to you under the Apache License, Version 2.0 (the
    + * "License"); you may not use this file except in compliance
    + * with the License.  You may obtain a copy of the License at
    + *
    + *
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +package org.apache.cassandra.db.streaming;
    +import org.apache.commons.lang3.builder.EqualsBuilder;
    +import org.apache.commons.lang3.builder.HashCodeBuilder;
    +import org.apache.cassandra.db.TypeSizes;
    +public class ComponentInfo
    --- End diff --
    Now, if you look carefully at all current uses of `ComponentInfo`, you'll see that it's
only ever being used as an element of lists, and never as a separate entity. As such it would
be cleaner - and nicer to work with - to implement a class, say, `ComponentManifest` that
would have an ordered map of `Component.Type` to `long` size, and expose the ordered keyset,
with serializers for the whole manifest. As it's written now, ser/deser code is leaking outside,
while it could instead be nicely encapsulated here.

> 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