ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1678) IgniteAtomicSequence: make following reservations in advance
Date Wed, 14 Sep 2016 07:56:20 GMT

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

Semen Boikov commented on IGNITE-1678:
--------------------------------------

Dmitry,

New tests added in this branch fail for me locally. Do they work for you? Do you have link
to TeamCity run (if you did not check TeamCity please do it)?

Thanks

> 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: 1.8
>
>
> 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
(v6.3.4#6332)

Mime
View raw message