harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Pervov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-5684) [drlvm][memory] Native memory management and tuning
Date Fri, 04 Apr 2008 07:21:24 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585431#action_12585431
] 

Pavel Pervov commented on HARMONY-5684:
---------------------------------------

Andrey,

Should we commit the patch and then work on it in trunk to escape rebasing nightmare?

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


Mime
View raw message