You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Sven Kobler-Morris (JIRA)" <ji...@apache.org> on 2014/08/27 10:44:58 UTC

[jira] [Updated] (OLINGO-415) Java client-proxy code getter method has performane issue

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

Sven Kobler-Morris updated OLINGO-415:
--------------------------------------

    Component/s:     (was: odata4-client)
                 odata4-client-JS

> Java client-proxy code getter method has performane issue
> ---------------------------------------------------------
>
>                 Key: OLINGO-415
>                 URL: https://issues.apache.org/jira/browse/OLINGO-415
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-client-JS
>    Affects Versions: V4 4.0.0-beta-01
>            Reporter: Challen
>            Assignee: Challen
>             Fix For: V4 4.0.0-beta-01
>
>
> when running with debugger attached, the below 100 times of .getDateTimeSent() takes 4s ~ 4.5s. (though without debugger attached, it can be a bit faster)
> ==================
>                        for (Message m : mc) {
> 				i++;
> 				date = m.getDateTimeSent();
> 			}
> ==================
> one of the causes: 
> AbstractStructuredInvocationHandler.invoke(..) method takes time to check (isSelfMethod()) first, then check (method.getName().startsWith("get")), so get- method on the proxy object is slowed down beause isSelfMethod() loops through all self methods by reflection.
> so the fix is to check get- set- first before checking isSelfMethod().



--
This message was sent by Atlassian JIRA
(v6.2#6252)