[ https://issues.apache.org/jira/browse/IGNITE-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15490389#comment-15490389 ]
Dmitriy Govorukhin commented on IGNITE-1678: -------------------------------------------- Unfortunately i get worse performance time. Master branch 1,038,823.05 op/sec, my branch 893 212.52 op/sec. I try to find problem and fix it. > 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)