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-444) improve throughput for normal inserts on many-core systems
Date Fri, 18 Sep 2009 15:09:16 GMT

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

Jonathan Ellis commented on CASSANDRA-444:
------------------------------------------

rebased (combining old patches 2 and 3) and added patches 3 and 4 to finish cleaning out memtableLock
in favor of Table.flusherLock

> improve throughput for normal inserts on many-core systems
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-444
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-444
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.5
>
>         Attachments: 0001-CASSANDRA-444-move-per-key-locking-inside-Memtable-and.txt,
0001-CASSANDRA-444-move-per-key-locking-inside-Memtable-and.txt, 0002-serialize-row-outside-of-commitlog-executor-to-improve.txt,
0002-serialize-row-outside-of-commitlog-executor-to-improve.txt, 0003-cleanup-r-m-unused-code.txt,
0003-use-putIfAbsent-to-avoid-locking-on-first-insert.txt, 0004-r-m-memtableLock-it-is-redundant-wrt-flusherLock.txt
>
>
> move the serialization of commitlog Row to the calling thread, not the CL executor
> shard the memtable lock
> others?

-- 
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