[
https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634660#comment-16634660
]
Ramesh Reddy commented on OLINGO-1302:
--------------------------------------
V2 and V4 are completely separate implementations. Have you separated or
clocked the server and client times separately?
If you like to profile V4 and provide details around bottlenecks then we can
take further look in improving.
> Performance: Olingo V4 is ten times slower than Olingo V2 when parsing query
> response body
> ------------------------------------------------------------------------------------------
>
> Key: OLINGO-1302
> URL: https://issues.apache.org/jira/browse/OLINGO-1302
> Project: Olingo
> Issue Type: Bug
> Components: odata4-client
> Affects Versions: (Java) V4 4.4.0
> Reporter: Scott Webster
> Priority: Critical
> Labels: performance
>
> The following request to the OData V2 Microsoft NorthWind source returns 500
> records with 26 columns:
> http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json
> The following request to the OData V4 Microsoft NorthWind source returns 500
> records with 26 columns:
> http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json
> When parsing the V2 response by calling the EntityProvider.readFeed() method,
> the elapsed time is 44 ms.
> When parsing the V4 response by calling the getBody() method on
> ODataRetrieveResponse<ClientEntitySet>, the elapsed time is 500 ms.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
