[jira] [Commented] (OLINGO-735) reflectionEquals in ClientItem and FullQualifiedName make for unacceptable parsing performance.

["Michael Bolz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OLINGO-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635042#comment-14635042 ] 

Michael Bolz commented on OLINGO-735:
-------------------------------------

Hi [~gmurray],

I agree with you that the use of {{reflectionEquals}} is not the best solution especially for {{ClientItem}} and {{FQN}}.
We will replace the usage of  {{reflectionEquals}} with an according implementation of both methods before the stable release.

Best regards,
Michael

> reflectionEquals in ClientItem and FullQualifiedName make for unacceptable parsing performance.
> -----------------------------------------------------------------------------------------------
>
>                 Key: OLINGO-735
>                 URL: https://issues.apache.org/jira/browse/OLINGO-735
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-client, odata4-commons
>    Affects Versions: (Java) V4 4.0.0-beta-03
>            Reporter: Graham Murray
>            Assignee: Michael Bolz
>             Fix For: (Java) V4 4.0.0
>
>
> Reviewing a CPU profiling result of a simple OData parse points out any use of reflectionEquals as demolishing the parse performance. It doesn't even seem like reflectionEquals is needed for ClientItem or FullQualifiedName, shouldn't they just be implemented properly?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)