[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.10) > 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 > 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)
[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 ] Aleksey Plekhanov updated IGNITE-1678: -- Fix Version/s: (was: 2.9) 2.10 > 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.10 > > 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)
[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)
[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 ] Dmitriy Govorukhin updated IGNITE-1678: --- Fix Version/s: (was: 2.7) 2.8 > 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.8 > > 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)
[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 ] Dmitriy Govorukhin updated IGNITE-1678: --- Ignite Flags: Docs Required > 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.7 > > 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)
[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 ] Dmitriy Pavlov updated IGNITE-1678: --- Fix Version/s: (was: 2.6) 2.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: Dmitriy Govorukhin >Priority: Major > Fix For: 2.7 > > 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)
[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 ] Andrey Gura updated IGNITE-1678: Fix Version/s: (was: 2.5) 2.6 > 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)
[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 ] Vladimir Ozerov updated IGNITE-1678: Fix Version/s: (was: 2.4) 2.5 > 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.5 > > 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)
[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 ] Vladimir Ozerov updated IGNITE-1678: Fix Version/s: (was: 2.3) 2.4 > 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: 2.4 > > 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 (v6.4.14#64029)
[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 ] Dmitriy Govorukhin updated IGNITE-1678: --- Fix Version/s: (was: 2.1) 2.2 > 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: 2.2 > > 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 (v6.3.15#6346)
[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 ] Dmitriy Govorukhin updated IGNITE-1678: --- Fix Version/s: (was: 2.0) 2.1 > 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: 2.1 > > 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 (v6.3.15#6346)
[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 ] Dmitriy Govorukhin updated IGNITE-1678: --- Attachment: Screenshot from 2016-12-15 10-50-22.png Performance between 1678-2 and master. > 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: 2.0 > > 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 (v6.3.4#6332)
[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 ] Dmitriy Govorukhin updated IGNITE-1678: --- Fix Version/s: (was: 1.8) 2.0 > 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: 2.0 > > > 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)
[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 ] Dmitriy Govorukhin updated IGNITE-1678: --- Assignee: Semen Boikov (was: Dmitriy Govorukhin) > 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: Semen Boikov > 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)
[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 ] Pavel Tupitsyn updated IGNITE-1678: --- Fix Version/s: (was: 1.7) 1.8 > 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.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)
[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 ] 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)
[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 ] Dmitriy Setrakyan updated IGNITE-1678: -- Assignee: Anton Vinogradov > 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: Anton Vinogradov > Fix For: 1.6 > > > 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)
[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 ] Dmitriy Setrakyan updated IGNITE-1678: -- Fix Version/s: 1.6 > 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: Anton Vinogradov > Fix For: 1.6 > > > 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)