[
https://issues.apache.org/jira/browse/CASSANDRA-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881584#comment-13881584
]
Jonathan Ellis edited comment on CASSANDRA-5549 at 1/25/14 1:10 AM:
--------------------------------------------------------------------
I think what I'm having a hard time with is, Pool should be a reservoir that we
allocate out of and instead it's a container of two such reservoirs (MT). I
propose renaming:
MemoryTracker -> Pool
Pool -> LinkedPools? DualPool? OnOffHeapPools? Reservoir? PoolPool?
Edit: isn't the traditional cop out name a Manager? I could go for
MemoryManager. :)
was (Author: jbellis):
I think what I'm having a hard time with is, Pool should be a reservoir that we
allocate out of and instead it's a container of two such reservoirs (MT). I
propose renaming:
MemoryTracker -> Pool
Pool -> LinkedPools? DualPool? OnOffHeapPools? Reservoir? PoolPool?
> Remove Table.switchLock
> -----------------------
>
> Key: CASSANDRA-5549
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5549
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jonathan Ellis
> Assignee: Benedict
> Labels: performance
> Fix For: 2.1
>
> Attachments: 5549-removed-switchlock.png, 5549-sunnyvale.png
>
>
> As discussed in CASSANDRA-5422, Table.switchLock is a bottleneck on the write
> path. ReentrantReadWriteLock is not lightweight, even if there is no
> contention per se between readers and writers of the lock (in Cassandra,
> memtable updates and switches).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
