[ https://issues.apache.org/jira/browse/IGNITE-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Artem Shutak updated IGNITE-1678: --------------------------------- Fix Version/s: (was: 1.6) 1.7 > 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: Artem Shutak > Fix For: 1.7 > > > 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)