[
https://issues.apache.org/jira/browse/CASSANDRA-9766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269625#comment-15269625
]
T Jake Luciani commented on CASSANDRA-9766:
-------------------------------------------
bq. ColumnIndex.create() is only called in BTW.append.
Good point I fixed this so its just re-used vs recycled.
bq. I would suggest leaving BTreeSearchIterator not recycled.
I agree. I removed all this in the last push. I'd like to revisit this though
in a later ticket.
bq. dob.recycle() should be in a finally since serializeRowBody() can throw.
done.
bq. I don't understand this line
I just did it for clarity.
bq. Why do we need to allocate cells lazily in BTreeRow.Builder
The cell builder is recycled on build(). Also the Row Builder is reset() on
build(). Sometimes the RowBuilder is re-used and sometimes its thrown away.
So by making the cell builder lazy we ensure the recycled object is only
allocated when the RowBuilder is re-used.
I also fixed the imports and kicked off the tests again.
> Bootstrap outgoing streaming speeds are much slower than during repair
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-9766
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9766
> Project: Cassandra
> Issue Type: Improvement
> Components: Streaming and Messaging
> Environment: Cassandra 2.1.2. more details in the pdf attached
> Reporter: Alexei K
> Assignee: T Jake Luciani
> Labels: performance
> Fix For: 3.x
>
> Attachments: problem.pdf
>
>
> I have a cluster in Amazon cloud , its described in detail in the attachment.
> What I've noticed is that we during bootstrap we never go above 12MB/sec
> transmission speeds and also those speeds flat line almost like we're hitting
> some sort of a limit ( this remains true for other tests that I've ran)
> however during the repair we see much higher,variable sending rates. I've
> provided network charts in the attachment as well . Is there an explanation
> for this? Is something wrong with my configuration, or is it a possible bug?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
