[
https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655569#comment-16655569
]
Ramesh Reddy commented on OLINGO-1302:
--------------------------------------
As I mentioned they are completely separate specifications and implementations.
The only thing in their lineage is the name. So, comparing one to one is like
apples to oranges. So, I do not think anyone did the performance testing
against each other.
so, if we want to dig more into it, we need to separate the query times from
client times. i.e. clock the service itself and find the times. Then the client
side parsing. So, far we have been focusing on client side parsing through your
perf testing. Is that also involves issuing the query to the server, or just
parsing? If we find some regression in parsing it should be simple to adjust,
if it is not then we need to further investigate.
> Performance: Olingo V4 is slower than Olingo V2 when de-serializing JSON
> 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
>
>
> Olingo V4 is slower than Olingo V2 when de-serializing the JSON response body.
> 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)
