[jira] Updated: (HARMONY-5684) [drlvm][memory] Native memory management and tuning

["Li-Gang Wang (JIRA)" <ji...@apache.org>]

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

Li-Gang Wang updated HARMONY-5684:
----------------------------------

    Attachment: memmgr2.patch

Chunrong, memmgr2.patch is able to fix the problem you found. The cause of the problem is just that the path of  MemoryPoolMXBean was wrongly specified in the original patch.
Please check if it works properly.

> [drlvm][memory] Native memory management and tuning
> ---------------------------------------------------
>
>                 Key: HARMONY-5684
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5684
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Andrey Yakushev
>            Assignee: Pavel Pervov
>         Attachments: memmgr.patch, memmgr.patch, memmgr2.patch
>
>
> There are several problems in DRLVM with native memory usage. For example:
> - Native memory usage couldn't be monitored currently in details via java.lang.management functionality
> - No explicit way to replace system native memory allocator to other memory managers in order to improve performance or footprint
> - Too many variants of the native memory allocations in DRLVM
> - Poor memory usage control (like leaks, double free calling, etc.)
> - Potential crash in diagnostics when OutOfMemory occur
> - Frequent native memory usage could cause OutOfMemory if GC wouldn't be timely called
> - No detail trace for the native memory usage
> Adding of some functionality to solve these would be hepful I think?

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