[jira] [Commented] (CASSANDRA-9468) Improvements to BufferPool

["Benedict (JIRA)" <ji...@apache.org>]

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

Benedict commented on CASSANDRA-9468:
-------------------------------------

With the full implementation of (4) - and some other minor tweaks - it should be noted this implementation can be generalized to cover memtables, commit log buffers, and likely any other buffer pooling we need (e.g. hints rewrite).

> Improvements to BufferPool
> --------------------------
>
>                 Key: CASSANDRA-9468
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9468
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Benedict
>            Assignee: Stefania
>            Priority: Minor
>             Fix For: 3.x
>
>
> Following up from CASSANDRA-8897, there are further improvements that can be made to the BufferPool:
> # The common code paths can be made non-atomic.
> # The chunk pool can be turned into a Stack, instead of a Queue, to improve the likelihood of cache presence
> # The chunk pool can be made processor-local, using e.g. [https://github.com/OpenHFT/Java-Thread-Affinity]
> # We can support smaller allocations by creating micro-chunks within each local pool, by allocating a single unit from the current chunk (or multiple units if we're about to discard a chunk that is not fully utilised).
> #* It should be possible to generalise this approach to make the entire allocation stack tiered, so that whenever you want a new chunk you go to the parent chunk that is an order of magnitude larger, and allocate a small slice (which you convert into a Chunk). Slices below a certain size can be taken exclusive ownership of, and above a certain size they remain shared.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)