ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Goncharuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1678) IgniteAtomicSequence: make following reservations in advance
Date Wed, 06 Jun 2018 11:12:00 GMT

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

Alexey Goncharuk commented on IGNITE-1678:
------------------------------------------

[~DmitriyGovorukhin] can you please pull master to your PR so we can re-run benchmarks?

> 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
>            Priority: Major
>             Fix For: 2.6
>
>         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
drops.
> 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
behavior.



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

Mime
View raw message