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

["Alexey Varlamov (JIRA)" <ji...@apache.org>]

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

Alexey Varlamov commented on HARMONY-5284:
------------------------------------------

Natalya, could you please expand on the following topics:
0) which application or workload you are trying to optimize, how do you measure the startup performance?
1) do you have any estimations or experimental data on this improvement? 
2) Do you have some profiling data pointing to this bottleneck or it is a wild guess?
3) Are there many classes with such a big number of members to benefit from hashing vs linear search? I'd expect such issue affecting overall VM execution far more than just reflection. What if we add hashing in reflection Java classes directly? 
4) From my POV the main benefit from the suggested patch (if any) might be caused by shorter path-lenght for obtaining some sole member of a class, i.e. one skips creating an array of all declared methods of the kind (methods/fields etc) for the 1st request. But how does it affect a long run of reflection-intensive apps ?

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