harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Berezhniuk (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-3991) [drlvm][jit] Memory management improvements in Jitrino compiler
Date Tue, 29 May 2007 23:28:16 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499970
] 

Ilya Berezhniuk commented on HARMONY-3991:
------------------------------------------

Mikhail,

I cannot reproduce such memory consumption for Test.java in interpreter mode.
I tried on 2 mashines and have got the following results:

single-core laptop 1Gb RAM
configuration               mem usage
ms512m/mx1024       579 = 512 + 67
ms256/mx512            314 = 256 + 58
ms128/mx256             183 = 128 + 65
default                           67  = 16  + 51

HT desktop 2Gb RAM
configuration               mem usage
ms512m/mx1024       579 = 512 + 67
ms256/mx512             315 = 256 + 59
ms128/mx256             183 = 128 + 65
default                           67  = 16  + 51

Thus memory consumption over allocated Java heap does not exceed 67Mb for me. I probably used
different way to start VM.

So could you please describe how did you started VM to get 1Gb consumption? And how did you
measure memory consumption?

> [drlvm][jit] Memory management improvements in Jitrino compiler
> ---------------------------------------------------------------
>
>                 Key: HARMONY-3991
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3991
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Mikhail Fursov
>            Assignee: Alexey Varlamov
>         Attachments: memory.diff, memory2.diff, Test.java
>
>
> Jitrino.OPT compiler allocates ~200*(bytecode method size) bytes before compiling a method.
> If the size of the method is large (~50Kb) and ~ 100-1000 threads concur to compile a
method the memory footprint can be very large: 1-10Gb
> The similar situation we have today with a real specjapp2004 benchmark.
> lock_method and unlock_method actions that force Jitrino to acquire locks for each compilation
session will not help today, because locking, as a PMF action, works after initial heap is
requested.

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


Mime
View raw message