[
https://issues.apache.org/jira/browse/CASSANDRA-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225878#comment-13225878
]
Michael Harris commented on CASSANDRA-4023:
-------------------------------------------
+1 on the patch. When we get a chance, we'll try out the patch on the cluster
that demonstrated the issue.
The overall intent of the ticket filed is that startup is slower overall, and
this was just one example in the code that I found that could be part of the
problem. Any other ideas as to things that could cause slower startup? We
noticed the logs had a lot of SSTables being opened during startup, and we do
have some 100+GB SSTables on disk, so general SSTable reading was my first
instinct to check.
> Improve BloomFilter deserialization performance
> -----------------------------------------------
>
> Key: CASSANDRA-4023
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4023
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.0.1
> Reporter: Joaquin Casares
> Assignee: Jonathan Ellis
> Priority: Minor
> Labels: datastax_qa
> Fix For: 1.0.9, 1.1.0
>
> Attachments: 4023.txt
>
>
> The difference of startup times between a 0.8.7 cluster and 1.0.7 cluster
> with the same amount of data is 4x greater in 1.0.7.
> It seems as though 1.0.7 loads the BloomFilter through a series of reading
> longs out in a multithreaded process while 0.8.7 reads the entire object.
> Perhaps we should update the new BloomFilter to do reading in batch as well?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
