[jira] [Updated] (IGNITE-5093) Better heap usage during exchange on large topologies and cache numbers/partitions.

2017-07-10 Thread Vladimir Ozerov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-5093:

Fix Version/s: (was: 2.1)
   2.2

> Better heap usage during exchange on large topologies and cache 
> numbers/partitions.
> ---
>
> Key: IGNITE-5093
> URL: https://issues.apache.org/jira/browse/IGNITE-5093
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
> Fix For: 2.2
>
>
> I observed huge heap occupation on large grid installation including 136 
> nodes/1k caches.
> Example from machine with 64g heap:
> {noformat}
>  num #instances #bytes  class name
> --
>1:   89728797743069822896  java.util.HashMap$Node
>2:   927316214866180592  [Ljava.util.HashMap$Node;
>3:   2012822924830775008java.lang.Integer
>4:   6247215983811096  [Ljava.lang.Object;
>5:   3383402767741664  [C
>6:   12188669411952   [B
>7:   9923859   635126976   java.util.HashMap
> ...
> {noformat}
> Further investigation had showed the heap is polluted during exchange 
> process, which involves creating many hashmaps occupying large amounts of 
> memory.
> Proposal: use other datastructures to help keep heap usage low.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5093) Better heap usage during exchange on large topologies and cache numbers/partitions.

2017-04-26 Thread Alexei Scherbakov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexei Scherbakov updated IGNITE-5093:
--
Description: 
I observed huge heap occupation during exchange on large grid installation 
including 136 nodes/1k caches.

Example from machine with 64g heap:

{noformat}
 num #instances #bytes  class name
--
   1:   89728797743069822896  java.util.HashMap$Node
   2:   927316214866180592  [Ljava.util.HashMap$Node;
   3:   2012822924830775008java.lang.Integer
   4:   6247215983811096  [Ljava.lang.Object;
   5:   3383402767741664  [C
   6:   12188669411952   [B
   7:   9923859   635126976   java.util.HashMap
...
{noformat}

Further investigation had showed the heap is polluted during exchange process, 
which involves creating many hashmaps occupying large amounts of memory.

Proposal: use other datastructures to help keep heap usage low.



  was:
I observed huge heap occupation during exchange on large grid installation 
including 136 nodes/1k caches.

Example from machine with 64g heap:

{noformat}
 num #instances #bytes  class name
--
   1:   89728797743069822896  java.util.HashMap$Node
   2:   927316214866180592  [Ljava.util.HashMap$Node;
   3:   2012822924830775008java.lang.Integer
   4:   6247215 983811096  [Ljava.lang.Object;
   5:   3383402 767741664  [C
   6:   12188  669411952   [B
   7:   9923859 635126976   java.util.HashMap
...
{noformat}

Further investigation had showed the heap is polluted during exchange process, 
which involves creating many hashmaps occupying large amounts of memory.

Proposal: use other datastructures to help keep heap usage low.




> Better heap usage during exchange on large topologies and cache 
> numbers/partitions.
> ---
>
> Key: IGNITE-5093
> URL: https://issues.apache.org/jira/browse/IGNITE-5093
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
> Fix For: 2.1
>
>
> I observed huge heap occupation during exchange on large grid installation 
> including 136 nodes/1k caches.
> Example from machine with 64g heap:
> {noformat}
>  num #instances #bytes  class name
> --
>1:   89728797743069822896  java.util.HashMap$Node
>2:   927316214866180592  [Ljava.util.HashMap$Node;
>3:   2012822924830775008java.lang.Integer
>4:   6247215983811096  [Ljava.lang.Object;
>5:   3383402767741664  [C
>6:   12188669411952   [B
>7:   9923859   635126976   java.util.HashMap
> ...
> {noformat}
> Further investigation had showed the heap is polluted during exchange 
> process, which involves creating many hashmaps occupying large amounts of 
> memory.
> Proposal: use other datastructures to help keep heap usage low.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5093) Better heap usage during exchange on large topologies and cache numbers/partitions.

2017-04-26 Thread Alexei Scherbakov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexei Scherbakov updated IGNITE-5093:
--
Description: 
I observed huge heap occupation on large grid installation including 136 
nodes/1k caches.

Example from machine with 64g heap:

{noformat}
 num #instances #bytes  class name
--
   1:   89728797743069822896  java.util.HashMap$Node
   2:   927316214866180592  [Ljava.util.HashMap$Node;
   3:   2012822924830775008java.lang.Integer
   4:   6247215983811096  [Ljava.lang.Object;
   5:   3383402767741664  [C
   6:   12188669411952   [B
   7:   9923859   635126976   java.util.HashMap
...
{noformat}

Further investigation had showed the heap is polluted during exchange process, 
which involves creating many hashmaps occupying large amounts of memory.

Proposal: use other datastructures to help keep heap usage low.



  was:
I observed huge heap occupation during exchange on large grid installation 
including 136 nodes/1k caches.

Example from machine with 64g heap:

{noformat}
 num #instances #bytes  class name
--
   1:   89728797743069822896  java.util.HashMap$Node
   2:   927316214866180592  [Ljava.util.HashMap$Node;
   3:   2012822924830775008java.lang.Integer
   4:   6247215983811096  [Ljava.lang.Object;
   5:   3383402767741664  [C
   6:   12188669411952   [B
   7:   9923859   635126976   java.util.HashMap
...
{noformat}

Further investigation had showed the heap is polluted during exchange process, 
which involves creating many hashmaps occupying large amounts of memory.

Proposal: use other datastructures to help keep heap usage low.




> Better heap usage during exchange on large topologies and cache 
> numbers/partitions.
> ---
>
> Key: IGNITE-5093
> URL: https://issues.apache.org/jira/browse/IGNITE-5093
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.6
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
> Fix For: 2.1
>
>
> I observed huge heap occupation on large grid installation including 136 
> nodes/1k caches.
> Example from machine with 64g heap:
> {noformat}
>  num #instances #bytes  class name
> --
>1:   89728797743069822896  java.util.HashMap$Node
>2:   927316214866180592  [Ljava.util.HashMap$Node;
>3:   2012822924830775008java.lang.Integer
>4:   6247215983811096  [Ljava.lang.Object;
>5:   3383402767741664  [C
>6:   12188669411952   [B
>7:   9923859   635126976   java.util.HashMap
> ...
> {noformat}
> Further investigation had showed the heap is polluted during exchange 
> process, which involves creating many hashmaps occupying large amounts of 
> memory.
> Proposal: use other datastructures to help keep heap usage low.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)