You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexey Varlamov (JIRA)" <ji...@apache.org> on 2007/05/28 18:11:15 UTC
[jira] Assigned: (HARMONY-3991) [drlvm][jit] Memory management
improvements in Jitrino compiler
[ https://issues.apache.org/jira/browse/HARMONY-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov reassigned HARMONY-3991:
----------------------------------------
Assignee: Alexey Varlamov
> [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
>
>
> 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.