You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/03 11:05:00 UTC
[jira] [Updated] (IGNITE-1678) IgniteAtomicSequence: make following
reservations in advance
[ https://issues.apache.org/jira/browse/IGNITE-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-1678:
------------------------------------
Fix Version/s: (was: 2.8)
2.9
> 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 A. Magda
> Assignee: Dmitriy Govorukhin
> Priority: Major
> Fix For: 2.9
>
> 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
(v8.3.4#803005)