[
https://issues.apache.org/jira/browse/CASSANDRA-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881666#comment-13881666
]
Jonathan Ellis commented on CASSANDRA-5549:
-------------------------------------------
bq. I can see your criticism of Pool being in fact two pools, but I think it
can also be viewed as just one. It only ever allocates one kind of resource,
but in some cases those resources may occupy memory both on and off heap.
Well, the real point is that we have two things (Pool/Allocator, MT/MO) that
operate on (connected on-off heap reservoirs / a single reservoir) and the
names should reflect that relationship.
> 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)
