You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Mikhail Fursov (JIRA)" <ji...@apache.org> on 2007/05/31 12:20:15 UTC

[jira] Created: (HARMONY-4010) [drlvm][jit] Memory management improvement in Jitrino.OPT compiler

[drlvm][jit] Memory management improvement in Jitrino.OPT compiler
------------------------------------------------------------------

                 Key: HARMONY-4010
                 URL: https://issues.apache.org/jira/browse/HARMONY-4010
             Project: Harmony
          Issue Type: Improvement
          Components: DRLVM
            Reporter: Mikhail Fursov


The MemoryManager class has "initial size" parameter and it's usage is misleading.

Once set this parameter works as default arena size for all arenas allocated by this memory manager.
I did a code review and see that in 90% of cases this parameter is not used correctly and default value is used (4k per arena).

The problem is that sometimes the initial size is set to very large values for a global memory managers (like 128*method size  which is about  5Mb for a large methods ). Once this parameter is set, every new arena in memory manager will have the same size, making JIT to ask a large memory chunks from OS when it's not needed and causing a problems in environments with high memory pressure.

I propose removing this parameter at all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (HARMONY-4010) [drlvm][jit] Memory management improvement in Jitrino.OPT compiler

Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Varlamov closed HARMONY-4010.
------------------------------------

    Resolution: Fixed

Applied at revision: 543442, thanks!

> [drlvm][jit] Memory management improvement in Jitrino.OPT compiler
> ------------------------------------------------------------------
>
>                 Key: HARMONY-4010
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4010
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Mikhail Fursov
>            Assignee: Alexey Varlamov
>         Attachments: mm.diff
>
>
> The MemoryManager class has "initial size" parameter and it's usage is misleading.
> Once set this parameter works as default arena size for all arenas allocated by this memory manager.
> I did a code review and see that in 90% of cases this parameter is not used correctly and default value is used (4k per arena).
> The problem is that sometimes the initial size is set to very large values for a global memory managers (like 128*method size  which is about  5Mb for a large methods ). Once this parameter is set, every new arena in memory manager will have the same size, making JIT to ask a large memory chunks from OS when it's not needed and causing a problems in environments with high memory pressure.
> I propose removing this parameter at all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HARMONY-4010) [drlvm][jit] Memory management improvement in Jitrino.OPT compiler

Posted by "Egor Pasko (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HARMONY-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500363 ] 

Egor Pasko commented on HARMONY-4010:
-------------------------------------

agreed

> [drlvm][jit] Memory management improvement in Jitrino.OPT compiler
> ------------------------------------------------------------------
>
>                 Key: HARMONY-4010
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4010
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Mikhail Fursov
>         Attachments: mm.diff
>
>
> The MemoryManager class has "initial size" parameter and it's usage is misleading.
> Once set this parameter works as default arena size for all arenas allocated by this memory manager.
> I did a code review and see that in 90% of cases this parameter is not used correctly and default value is used (4k per arena).
> The problem is that sometimes the initial size is set to very large values for a global memory managers (like 128*method size  which is about  5Mb for a large methods ). Once this parameter is set, every new arena in memory manager will have the same size, making JIT to ask a large memory chunks from OS when it's not needed and causing a problems in environments with high memory pressure.
> I propose removing this parameter at all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (HARMONY-4010) [drlvm][jit] Memory management improvement in Jitrino.OPT compiler

Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Varlamov reassigned HARMONY-4010:
----------------------------------------

    Assignee: Alexey Varlamov

> [drlvm][jit] Memory management improvement in Jitrino.OPT compiler
> ------------------------------------------------------------------
>
>                 Key: HARMONY-4010
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4010
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Mikhail Fursov
>            Assignee: Alexey Varlamov
>         Attachments: mm.diff
>
>
> The MemoryManager class has "initial size" parameter and it's usage is misleading.
> Once set this parameter works as default arena size for all arenas allocated by this memory manager.
> I did a code review and see that in 90% of cases this parameter is not used correctly and default value is used (4k per arena).
> The problem is that sometimes the initial size is set to very large values for a global memory managers (like 128*method size  which is about  5Mb for a large methods ). Once this parameter is set, every new arena in memory manager will have the same size, making JIT to ask a large memory chunks from OS when it's not needed and causing a problems in environments with high memory pressure.
> I propose removing this parameter at all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HARMONY-4010) [drlvm][jit] Memory management improvement in Jitrino.OPT compiler

Posted by "Mikhail Fursov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikhail Fursov updated HARMONY-4010:
------------------------------------

    Attachment: mm.diff

> [drlvm][jit] Memory management improvement in Jitrino.OPT compiler
> ------------------------------------------------------------------
>
>                 Key: HARMONY-4010
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4010
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Mikhail Fursov
>         Attachments: mm.diff
>
>
> The MemoryManager class has "initial size" parameter and it's usage is misleading.
> Once set this parameter works as default arena size for all arenas allocated by this memory manager.
> I did a code review and see that in 90% of cases this parameter is not used correctly and default value is used (4k per arena).
> The problem is that sometimes the initial size is set to very large values for a global memory managers (like 128*method size  which is about  5Mb for a large methods ). Once this parameter is set, every new arena in memory manager will have the same size, making JIT to ask a large memory chunks from OS when it's not needed and causing a problems in environments with high memory pressure.
> I propose removing this parameter at all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.