harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-3991) [drlvm][jit] Memory management improvements in Jitrino compiler
Date Wed, 30 May 2007 05:44:16 GMT

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

Alexey Varlamov commented on HARMONY-3991:
------------------------------------------

The memory2.diff is applied at revision: 542754.
If VM memory over-consumption is confirmed, I suggest we close this issue and create a separate
one for VM.
Do you think we need to add this test to regression suite?

> [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