cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1891) large supercolumn deserialization invokes CSLM worst case scenario
Date Tue, 04 Jan 2011 22:55:46 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977518#action_12977518
] 

Jonathan Ellis commented on CASSANDRA-1891:
-------------------------------------------

building a treemap is a lot more heavyweight than the SortedMap facade here, though.  (and
sorted input is also worst-case there.)

Java could use a DictMixIn. :)

> large supercolumn deserialization invokes CSLM worst case scenario
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-1891
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1891
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Cliff Moon
>            Priority: Minor
>             Fix For: 0.7.1
>
>         Attachments: 1891-v2.txt, supercolumn.patch
>
>
> SuperColumn deserialization hits a worst case insert scenario for CSLM: inserting pre-sorted
entries one at a time.  Inside of CSLM this requires scanning to the end of the list and doing
a comparison at every step for every item inserted.  This patch supplies a SortedMap interface
to the supercolumn deserialization.  CSLM will do a bulk insert from a SortedMap interface
supplied in the constructor.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message