Punith DG created OLINGO-1618:
---------------------------------

             Summary: Performance degradation with read entity api from version 
4.9.0
                 Key: OLINGO-1618
                 URL: https://issues.apache.org/jira/browse/OLINGO-1618
             Project: Olingo
          Issue Type: Question
          Components: odata4-client
    Affects Versions: (Java) V4 4.9.0
            Reporter: Punith DG


Hi Olingo Communtiy,


We use Olingo libraries to parse OData responses.
Recently we have upgraded the Olingo libraries from 4.2.0 to 4.9.0 version.
After upgrading the jars we are seeing a huge performance impact while reading 
the entity set form the input stream of back-end response.

We are specifically talking about following API that is getting slow

*org.apache.olingo.client.core.serialization.ODataReaderImpl.readEntitySet(InputStream,
 ContentType)*

Previously, with Olingo jars *version 4.2.0* it was taking around *30sec* to 
read and parse the entityset.

With upgraded Olingo jars *version 4.9.0* it is taking around *2min 30 sec* to 
parse the same amount of data.

Following is the list of jars that we have upgraded.

odata-client-api-4.9.0.jar
odata-client-core-4.9.0.jar
odata-commons-api-4.9.0.jar
odata-commons-core-4.9.0.jar

We have updated these jars to latest Olingo library version (5.0.0) but still 
the same slowness was observed.

We also tried various combination of jackson-databind library version and 
checked if it impacts the performance but it did not help.

As shown below, all these combinations took long time to complete
With jackson-databind (2.10.1) and olingo jars(4.9.0) time taken: *2min 29s*
With jackson-databind(2.13.1) and  olingo jars(4.9.0) time taken: *3min 3s*
With  jackson-databind(2.13.1) and olingo jars(5.0.0) time taken: *2min 20s*

While checking the commits around serialization I see this Jira number not sure 
if this fix is related and can fix the slowness issue
https://issues.apache.org/jira/browse/OLINGO-1609

Highly appreciate your quick response.
 
Thanks & best regards,
Punith



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to