[jira] [Commented] (ARTEMIS-2321) Paging scalability and GC improvements

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on ARTEMIS-2321:
----------------------------------------------------------

Commit 30c82f43b0f3d602bba5bc0a962de590a4afde63 in activemq-artemis's branch refs/heads/master from Francesco Nigro
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=30c82f4 ]

ARTEMIS-2321 PageCursorInfo caches number of msgs to save Page::read


> Paging scalability and GC improvements
> --------------------------------------
>
>                 Key: ARTEMIS-2321
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2321
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 2.8.0
>            Reporter: Francesco Nigro
>            Priority: Major
>             Fix For: 2.9.0
>
>          Time Spent: 11h 40m
>  Remaining Estimate: 0h
>
> PageCursorProviderImpl::getPageCache's on cache miss is blocking the whole softCache until the requested page isn't fully read, making other threads unable to make progress by querying the cache.
> It would be better to make the page read operation a non-blocking operation for the whole cache, allowing threads that need different pageId to make progress.
> Other improvements:
> * PageCursorProviderImpl can use specialized primitive hash maps to reduce memory footprint (that would cause some page entries to be collected prematurely)
> * PageCache children can avoid to maintain a reference to a Page
> * PagingStoreImpl perform many unnecessary volatile stores/loads and some fields can be turned into plain ones, avoiding expensive atomic operations



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)