ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Govorukhin (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-1678) IgniteAtomicSequence: make following reservations in advance
Date Thu, 15 Dec 2016 07:59:58 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15750704#comment-15750704

Dmitriy Govorukhin edited comment on IGNITE-1678 at 12/15/16 7:58 AM:

I got the following results, see attach. All changes in branch [1678-2|https://github.com/gridgain/apache-ignite/tree/ignite-1678-2]

was (Author: dmitriygovorukhin):
I got the following results, see attach. 

> IgniteAtomicSequence: make following reservations in advance
> ------------------------------------------------------------
>                 Key: IGNITE-1678
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1678
>             Project: Ignite
>          Issue Type: Improvement
>          Components: data structures
>    Affects Versions: ignite-1.4
>            Reporter: Denis Magda
>            Assignee: Dmitriy Govorukhin
>             Fix For: 2.0
>         Attachments: Screenshot from 2016-12-15 10-50-22.png
> In current implementation a new reservation is made when the current local sequence boundary
is exceeded.
> In cases when there are many nodes that use the same atomic sequence there can be a situation
when all the nodes start doing a new reservation at the same time. This can lead to performance
> As a performance optimization it makes sense to start reserving new sequence slot in
advance (in background), like when around 80% of current reservation has already been used.
Probably we should add a special parameter to {{AtomicConfiguration}} that will manage such

This message was sent by Atlassian JIRA

View raw message