cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4023) Improve BloomFilter deserialization performance
Date Fri, 23 Mar 2012 22:25:29 GMT


Yuki Morishita updated CASSANDRA-4023:

    Attachment: 0001-fix-loading-promoted-row-index.patch

Attaching patch to current trunk.

Unfortunately, there is no way to determine serialized size of promoted row index without
actually deserializing some of it, so we cannot determine the last key.
Patch deserializes every key when sstable has promoted index, but instead it tries to reduce
the amount of io when deserialize index itself.
> Improve BloomFilter deserialization performance
> -----------------------------------------------
>                 Key: CASSANDRA-4023
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0.1
>            Reporter: Joaquin Casares
>            Assignee: Yuki Morishita
>            Priority: Minor
>              Labels: datastax_qa
>             Fix For: 1.0.9, 1.1.0
>         Attachments: 0001-fix-loading-promoted-row-index.patch, 4023.txt, cassandra-1.0-4023-v2.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:!default.jspa
For more information on JIRA, see:


View raw message