[
https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Webster updated OLINGO-1302:
----------------------------------
Description:
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 approximately 180 ms.
When parsing the V4 response by calling the getODataEntitySet() method, the
elapsed time is approximately 320 ms.
I have attached a zipped up Eclipse project (olingo-performance-test) which
contains two Java programs (TestOlingoV2.java, TestOlingoV4.java).
These programs can be run to compare the performance of the JSON
deserialization in Olingo V2 and V4.
The Northwind metadata and the JSON response body are read from files included
in the project.
I have attached a snapshot image from a SAP Java Profiling tool showing
profiling on the TestOlingoV4 program.
was:
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 approximately 180 ms.
When parsing the V4 response by calling the getODataEntitySet() method, the
elapsed time is approximately 320 ms.
I have attached a zipped up Eclipse project (olingo-performance-test) which
contains two Java programs (TestOlingoV2.java, TestOlingoV4.java).
These programs can be run to compare the performance of the JSON
deserialization in Olingo V2 and V4.
The Northwind metadata and the JSON response body are read from files included
in the project.
> 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
> Attachments: TestOlingoV4.Profiling.PNG, olingo-performance-test.zip
>
>
> 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 approximately 180 ms.
> When parsing the V4 response by calling the getODataEntitySet() method, the
> elapsed time is approximately 320 ms.
> I have attached a zipped up Eclipse project (olingo-performance-test) which
> contains two Java programs (TestOlingoV2.java, TestOlingoV4.java).
> These programs can be run to compare the performance of the JSON
> deserialization in Olingo V2 and V4.
> The Northwind metadata and the JSON response body are read from files
> included in the project.
> I have attached a snapshot image from a SAP Java Profiling tool showing
> profiling on the TestOlingoV4 program.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
