olingo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Webster (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OLINGO-1302) Performance: Olingo V4 is slower than Olingo V2 when parsing query response body
Date Mon, 15 Oct 2018 21:50:00 GMT

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

Scott Webster updated OLINGO-1302:
----------------------------------
    Summary: Performance: Olingo V4 is slower than Olingo V2 when parsing query response body
 (was: Performance: Olingo V4 is ten times slower than Olingo V2 when parsing query response
body)

> Performance: Olingo V4 is 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)

Mime
View raw message