You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Naumova Natalya (JIRA)" <ji...@apache.org> on 2008/01/29 11:23:34 UTC

[jira] Commented: (HARMONY-5284) [drlvm][startup][performance] classloading - lookup for methods and fields

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

Naumova Natalya  commented on HARMONY-5284:
-------------------------------------------

Sorry for delay:
0) I've made some measurements on large graphic application with AWT/SWING usage, the performance was measured by time from start till end with  jemmy library usage and simple "/usr/bin/time" commandline. 
1) this gave ~5% boost on EIOffice startup
2) yes, Class.getMethod was on the top of the hot methods when Eclipse.TPTP analisys was done.
3) ofcourse we can do hashing in java code, but it's more convinient and faster when all the searches are done in the same place, I mean all the lookups are leading to the Class.lookup_method(..);


> [drlvm][startup][performance] classloading - lookup for methods and fields
> --------------------------------------------------------------------------
>
>                 Key: HARMONY-5284
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5284
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: DRLVM
>            Reporter: Naumova Natalya 
>
> It's for better lookup procedures for methods and fileds resolving; moving Class.getMethod to JNI :
> There was just linear search for lookup methods and fileds in DRLVM, so using hash for lookup improves the performance on startup.

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