[jira] [Updated] (IGNITE-2274) Avoid ArrayList creation for a single element when possible.
[ https://issues.apache.org/jira/browse/IGNITE-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2274: Fix Version/s: (was: 2.1) 2.2 > Avoid ArrayList creation for a single element when possible. > > > Key: IGNITE-2274 > URL: https://issues.apache.org/jira/browse/IGNITE-2274 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Priority: Minor > Labels: performance > Fix For: 2.2 > > > Profiling shown lots of ArrayList allocations. Investigation shown the > following usual pattern in our code: > 1) Create empty ArrayList. > 2) Then add a single element to it at some point. When this addition happens, > ArrayList allocates Object[10] array. > But in lots cases we know in advance that particular senario will contain > only single entry in this collection. > Need to fix places where it is trivial to detect and handle. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-2274) Avoid ArrayList creation for a single element when possible.
[ https://issues.apache.org/jira/browse/IGNITE-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2274: Fix Version/s: (was: 2.0) 2.1 > Avoid ArrayList creation for a single element when possible. > > > Key: IGNITE-2274 > URL: https://issues.apache.org/jira/browse/IGNITE-2274 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Priority: Minor > Labels: performance > Fix For: 2.1 > > > Profiling shown lots of ArrayList allocations. Investigation shown the > following usual pattern in our code: > 1) Create empty ArrayList. > 2) Then add a single element to it at some point. When this addition happens, > ArrayList allocates Object[10] array. > But in lots cases we know in advance that particular senario will contain > only single entry in this collection. > Need to fix places where it is trivial to detect and handle. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (IGNITE-2274) Avoid ArrayList creation for a single element when possible.
[ https://issues.apache.org/jira/browse/IGNITE-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2274: Priority: Minor (was: Major) > Avoid ArrayList creation for a single element when possible. > > > Key: IGNITE-2274 > URL: https://issues.apache.org/jira/browse/IGNITE-2274 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Priority: Minor > Labels: performance > Fix For: 2.0 > > > Profiling shown lots of ArrayList allocations. Investigation shown the > following usual pattern in our code: > 1) Create empty ArrayList. > 2) Then add a single element to it at some point. When this addition happens, > ArrayList allocates Object[10] array. > But in lots cases we know in advance that particular senario will contain > only single entry in this collection. > Need to fix places where it is trivial to detect and handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2274) Avoid ArrayList creation for a single element when possible.
[ https://issues.apache.org/jira/browse/IGNITE-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2274: Fix Version/s: (was: 1.8) 2.0 > Avoid ArrayList creation for a single element when possible. > > > Key: IGNITE-2274 > URL: https://issues.apache.org/jira/browse/IGNITE-2274 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov > Labels: performance > Fix For: 2.0 > > > Profiling shown lots of ArrayList allocations. Investigation shown the > following usual pattern in our code: > 1) Create empty ArrayList. > 2) Then add a single element to it at some point. When this addition happens, > ArrayList allocates Object[10] array. > But in lots cases we know in advance that particular senario will contain > only single entry in this collection. > Need to fix places where it is trivial to detect and handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2274) Avoid ArrayList creation for a single element when possible.
[ https://issues.apache.org/jira/browse/IGNITE-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2274: Fix Version/s: (was: 1.6) 1.7 > Avoid ArrayList creation for a single element when possible. > > > Key: IGNITE-2274 > URL: https://issues.apache.org/jira/browse/IGNITE-2274 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov > Labels: performance > Fix For: 1.7 > > > Profiling shown lots of ArrayList allocations. Investigation shown the > following usual pattern in our code: > 1) Create empty ArrayList. > 2) Then add a single element to it at some point. When this addition happens, > ArrayList allocates Object[10] array. > But in lots cases we know in advance that particular senario will contain > only single entry in this collection. > Need to fix places where it is trivial to detect and handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2274) Avoid ArrayList creation for a single element when possible.
[ https://issues.apache.org/jira/browse/IGNITE-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2274: Issue Type: Task (was: Sub-task) Parent: (was: IGNITE-2232) > Avoid ArrayList creation for a single element when possible. > > > Key: IGNITE-2274 > URL: https://issues.apache.org/jira/browse/IGNITE-2274 > Project: Ignite > Issue Type: Task > Components: general >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov > Labels: performance > Fix For: 1.6 > > > Profiling shown lots of ArrayList allocations. Investigation shown the > following usual pattern in our code: > 1) Create empty ArrayList. > 2) Then add a single element to it at some point. When this addition happens, > ArrayList allocates Object[10] array. > But in lots cases we know in advance that particular senario will contain > only single entry in this collection. > Need to fix places where it is trivial to detect and handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2274) Avoid ArrayList creation for a single element when possible.
[ https://issues.apache.org/jira/browse/IGNITE-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2274: Labels: performance (was: ) > Avoid ArrayList creation for a single element when possible. > > > Key: IGNITE-2274 > URL: https://issues.apache.org/jira/browse/IGNITE-2274 > Project: Ignite > Issue Type: Sub-task > Components: general >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov > Labels: performance > Fix For: 1.6 > > > Profiling shown lots of ArrayList allocations. Investigation shown the > following usual pattern in our code: > 1) Create empty ArrayList. > 2) Then add a single element to it at some point. When this addition happens, > ArrayList allocates Object[10] array. > But in lots cases we know in advance that particular senario will contain > only single entry in this collection. > Need to fix places where it is trivial to detect and handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2274) Avoid ArrayList creation for a single element when possible.
[ https://issues.apache.org/jira/browse/IGNITE-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-2274: Assignee: (was: Vladimir Ozerov) > Avoid ArrayList creation for a single element when possible. > > > Key: IGNITE-2274 > URL: https://issues.apache.org/jira/browse/IGNITE-2274 > Project: Ignite > Issue Type: Sub-task > Components: general >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov > Fix For: 1.6 > > > Profiling shown lots of ArrayList allocations. Investigation shown the > following usual pattern in our code: > 1) Create empty ArrayList. > 2) Then add a single element to it at some point. When this addition happens, > ArrayList allocates Object[10] array. > But in lots cases we know in advance that particular senario will contain > only single entry in this collection. > Need to fix places where it is trivial to detect and handle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
