You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2011/12/21 19:43:32 UTC
[jira] [Issue Comment Edited] (CASSANDRA-2893) Add row-level
isolation
[ https://issues.apache.org/jira/browse/CASSANDRA-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174290#comment-13174290 ]
Brandon Williams edited comment on CASSANDRA-2893 at 12/21/11 6:43 PM:
-----------------------------------------------------------------------
I tested both trunk and trunk w/2893 applied. I did 100M+ appends to a single row in each case with 300 threads/conns at a time. Attached is a chart of the write latency histogram for both.
The median latency was the same, though overall 2893 was higher. Overall this doesn't seem _too_ bad, especially considering 300 clients contending for a single row isn't too common a scenario.
Throughput was roughly the same for both (2893 was actually a tiny bit faster, but well within standard deviation.)
was (Author: brandon.williams):
I tested both trunk and trunk w/2893 applied. I did 100M+ appends to a single row in each case with 300 threads/conns at a time. Here is a chart of the write latency histogram for both:
!latency.svg!
The median latency was the same, though overall 2893 was higher. Overall this doesn't seem _too_ bad, especially considering 300 clients contending for a single row isn't too common a scenario.
Throughput was roughly the same for both (2893 was actually a tiny bit faster, but well within standard deviation.)
> Add row-level isolation
> -----------------------
>
> Key: CASSANDRA-2893
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2893
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 1.1
>
> Attachments: 0001-Move-deletion-infos-into-ISortedColumns-v2.patch, 0001-Move-deletion-infos-into-ISortedColumns.patch, 0002-Make-memtable-use-CF.addAll-v2.patch, 0002-Make-memtable-use-CF.addAll.patch, 0003-Add-AtomicSortedColumn-and-snapTree-v2.patch, 0003-Add-AtomicSortedColumn-and-snapTree.patch, latency.svg, snaptree-0.1-SNAPSHOT.jar
>
>
> This could be done using an the atomic ConcurrentMap operations from the Memtable and something like http://code.google.com/p/pcollections/ to replace the ConcurrentSkipListMap in ThreadSafeSortedColumns. The trick is that pcollections does not provide a SortedMap, so we probably need to write our own.
> Googling [persistent sortedmap] I found http://code.google.com/p/actord/source/browse/trunk/actord/src/main/scala/ff/collection (in scala) and http://clojure.org/data_structures#Data Structures-Maps.
--
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