You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Goffinet (JIRA)" <ji...@apache.org> on 2009/09/21 05:52:16 UTC
[jira] Closed: (CASSANDRA-444) improve throughput for normal
inserts on many-core systems
[ https://issues.apache.org/jira/browse/CASSANDRA-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Goffinet closed CASSANDRA-444.
------------------------------------
> 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.