[
https://issues.apache.org/jira/browse/OLINGO-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Amend resolved OLINGO-735.
------------------------------------
Resolution: Fixed
Assignee: Christian Amend (was: Michael Bolz)
Hi,
I removed the reflection equals call for all client items with this commit:
https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=a1731b7efefbda0bf9574d6a82b51a9ab77bb010
Could you please test with the current SNAPSHOT and let me know if this fixes
your issues?
Best Regards,
Christian
> 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: Christian Amend
> 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)
