harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Beliaev (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-4914) [drlvm] increasing default sizes for code and vtable pools give a little boost
Date Mon, 15 Oct 2007 11:41:50 GMT

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

Vladimir Beliaev commented on HARMONY-4914:
-------------------------------------------

My concern is that such changes should be carefully tested (not only with the help of acceptance
tests). They looks simple, still I'm not sure there is no related restrictions hardcoded somewhere
in VM code which would conflict with the proposed increasing. 


> [drlvm]  increasing default sizes for code and vtable pools give a little boost
> -------------------------------------------------------------------------------
>
>                 Key: HARMONY-4914
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4914
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>         Environment: windows, linux
>            Reporter: Rustem Rafikov
>            Priority: Minor
>         Attachments: code-size.patch
>
>
> I suggest to increase the default sizes for vtable and code pools (see vm/vmcore/include/mem_alloc.h).
> It reduces fragmentation of data and thus gives a little boost on specjbb2005 (as example).

> For example, the default code pool size for bootstrap classloader is 256K. Final size
is about 2Mb, so it is reallocated ~6-7 times. The numbers for default classloader are: 64K
- default, ~800K - final, it is  realocated 11-12 times. 
> The patch is attached.

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