[jira] Updated: (HARMONY-3991) [drlvm][jit] Memory management improvements in Jitrino compiler

["Mikhail Fursov (JIRA)" <ji...@apache.org>]

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

Mikhail Fursov updated HARMONY-3991:
------------------------------------

    Attachment: memory.diff

This patch moves all preallocation in Jitrino.OPT to opt_init action and allows using lock/unlock actions to deal with situations like described above.

Here is an example of CMD line option for -Xem:opt mode with locks moved from 'codegen' alias to global path level.

XX:jit.CS_OPT.path=lock_method,opt_init,translator,optimizer,hir2lir,codegen,unlock_method

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