[jira] [Commented] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[ https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14354278#comment-14354278 ] Karuna Joshi commented on OLINGO-527: - Hi Michael / Chandan According to JIRA-414, filter on $expand is not supported. I wanted to know of this is fixed or any plan to fix or any work around of this? We want to apply filter on main entity and expanded entity as well Thanks Is there any possible ay to reduce build response time of JPA query Key: OLINGO-527 URL: https://issues.apache.org/jira/browse/OLINGO-527 Project: Olingo Issue Type: Question Components: odata2-core, odata2-jpa Reporter: Karuna Joshi Assignee: Chandan V.A We have a very large data base and we are exposing the data using olingo restful web service. when I compare, time taken to execute the same query via jdbc connection and time taken by olingo, there is a significant difference. Time taken by Olingo is very large. Time taken to process JPA query + Time taken to build response is the total time taken by olingo. We try to tune the JPA queries using Query hints, but still build response time is also very large. I have a question : Is there any way we can reduce the time taken to build the response ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[ https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14339866#comment-14339866 ] Karuna Joshi commented on OLINGO-527: - Thanks for the reply ! One question, does OLINGO 2 or OLINGO 4 support applying filter on expanded entity or do you have any plan to support it ? Is there any possible ay to reduce build response time of JPA query Key: OLINGO-527 URL: https://issues.apache.org/jira/browse/OLINGO-527 Project: Olingo Issue Type: Question Components: odata2-core, odata2-jpa Reporter: Karuna Joshi Assignee: Chandan V.A We have a very large data base and we are exposing the data using olingo restful web service. when I compare, time taken to execute the same query via jdbc connection and time taken by olingo, there is a significant difference. Time taken by Olingo is very large. Time taken to process JPA query + Time taken to build response is the total time taken by olingo. We try to tune the JPA queries using Query hints, but still build response time is also very large. I have a question : Is there any way we can reduce the time taken to build the response ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[ https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14338094#comment-14338094 ] Karuna Joshi commented on OLINGO-527: - Just an additional info - We are using JPA processor Is there any possible ay to reduce build response time of JPA query Key: OLINGO-527 URL: https://issues.apache.org/jira/browse/OLINGO-527 Project: Olingo Issue Type: Question Components: odata2-core, odata2-jpa Reporter: Karuna Joshi Assignee: Chandan V.A We have a very large data base and we are exposing the data using olingo restful web service. when I compare, time taken to execute the same query via jdbc connection and time taken by olingo, there is a significant difference. Time taken by Olingo is very large. Time taken to process JPA query + Time taken to build response is the total time taken by olingo. We try to tune the JPA queries using Query hints, but still build response time is also very large. I have a question : Is there any way we can reduce the time taken to build the response ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[ https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14338224#comment-14338224 ] Chandan V.A commented on OLINGO-527: Hello Karuna, If you set the page size olingo will generare the next link. Regards Chandan Is there any possible ay to reduce build response time of JPA query Key: OLINGO-527 URL: https://issues.apache.org/jira/browse/OLINGO-527 Project: Olingo Issue Type: Question Components: odata2-core, odata2-jpa Reporter: Karuna Joshi Assignee: Chandan V.A We have a very large data base and we are exposing the data using olingo restful web service. when I compare, time taken to execute the same query via jdbc connection and time taken by olingo, there is a significant difference. Time taken by Olingo is very large. Time taken to process JPA query + Time taken to build response is the total time taken by olingo. We try to tune the JPA queries using Query hints, but still build response time is also very large. I have a question : Is there any way we can reduce the time taken to build the response ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[ https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14338060#comment-14338060 ] Karuna Joshi commented on OLINGO-527: - Hi Chandan We have tried using json but the response build time does not vary much. Our service is using OLINGO 2 lib. If I use server side pagination using SetPageSize() then does OLINGO provide next page link or we have to do it ? Does OLINGO 4 support applying filter on expanded entity? If not is there any way I can apply filter on $expand entity ? Thank you Is there any possible ay to reduce build response time of JPA query Key: OLINGO-527 URL: https://issues.apache.org/jira/browse/OLINGO-527 Project: Olingo Issue Type: Question Components: odata2-core, odata2-jpa Reporter: Karuna Joshi Assignee: Chandan V.A We have a very large data base and we are exposing the data using olingo restful web service. when I compare, time taken to execute the same query via jdbc connection and time taken by olingo, there is a significant difference. Time taken by Olingo is very large. Time taken to process JPA query + Time taken to build response is the total time taken by olingo. We try to tune the JPA queries using Query hints, but still build response time is also very large. I have a question : Is there any way we can reduce the time taken to build the response ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[ https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14323770#comment-14323770 ] Chandan V.A commented on OLINGO-527: Hello Karuna, Did you try with JSON payload format. JSON payload is lighter and compact. Please check whether you face significant performance issue with JSON format as well. Regards Chandan Is there any possible ay to reduce build response time of JPA query Key: OLINGO-527 URL: https://issues.apache.org/jira/browse/OLINGO-527 Project: Olingo Issue Type: Question Reporter: Karuna Joshi We have a very large data base and we are exposing the data using olingo restful web service. when I compare, time taken to execute the same query via jdbc connection and time taken by olingo, there is a significant difference. Time taken by Olingo is very large. Time taken to process JPA query + Time taken to build response is the total time taken by olingo. We try to tune the JPA queries using Query hints, but still build response time is also very large. I have a question : Is there any way we can reduce the time taken to build the response ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[
https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318669#comment-14318669
]
Karuna Joshi commented on OLINGO-527:
-
Hi Chandan,
around 15000 records fetched from DB. we tried to set the limit to fetch around
3000 record at a time using eclipselink fetch-size property in
persistence.xml. we also try to use SKIP AND TOP in data request url.
The main problem is, even if we bear the delay in large number of records being
fetched (in subsequent hit its taking very less time ) , the time taken to
build the response for such a huge dataset is very large. Time taken to build
the response is large, when we use $expand in request. But without expand if
the same number of records are fetched, build response time is very very less.
I looked into the olingo code where it build response and found that major time
is taken in AtomEntryEntityProducer::append function. which is being called in
for loop for each entry in data map.
specially in this block of AtomEntryEntityProducer::append
else {
// write all links
if (!properties.isContentOnly()) {
appendAtomEditLink(writer, eia, data, selfLink);
appendAtomNavigationLinks(writer, eia, data);
} else {
appendAdditinalLinks(writer, eia, data);
}
// write properties/content
appendCustomProperties(writer, eia, data);
writer.writeStartElement(FormatXml.ATOM_CONTENT);
writer.writeAttribute(FormatXml.ATOM_TYPE,
ContentType.APPLICATION_XML.toString());
appendProperties(writer, eia, data);
writer.writeEndElement();
}
this block call appendAtomNavigationLinks() function which in turn call the
same append function in turn.
wanted to know is there anything we are missing, or should do to improve the
time taken to build the response ? can it be related to JPA entity relationship
we define ?
we can not use delta token feature as user can request any data any resource.
we can not be sure about what should be our delta in advance.
Thank you !
Is there any possible ay to reduce build response time of JPA query
Key: OLINGO-527
URL: https://issues.apache.org/jira/browse/OLINGO-527
Project: Olingo
Issue Type: Question
Reporter: Karuna Joshi
We have a very large data base and we are exposing the data using olingo
restful web service. when I compare, time taken to execute the same query via
jdbc connection and time taken by olingo, there is a significant difference.
Time taken by Olingo is very large.
Time taken to process JPA query + Time taken to build response is the total
time taken by olingo.
We try to tune the JPA queries using Query hints, but still build response
time is also very large.
I have a question :
Is there any way we can reduce the time taken to build the response ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OLINGO-527) Is there any possible ay to reduce build response time of JPA query
[ https://issues.apache.org/jira/browse/OLINGO-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14300118#comment-14300118 ] Chandan V.A commented on OLINGO-527: Hello Karuna, How many records are getting fetched from DB? You could try paging and delta token features supported in Olingo JPA processor to restrict the number of records that are fetched from the DB. Thanks Kind Regards Chandan Is there any possible ay to reduce build response time of JPA query Key: OLINGO-527 URL: https://issues.apache.org/jira/browse/OLINGO-527 Project: Olingo Issue Type: Question Reporter: Karuna Joshi We have a very large data base and we are exposing the data using olingo restful web service. when I compare, time taken to execute the same query via jdbc connection and time taken by olingo, there is a significant difference. Time taken by Olingo is very large. Time taken to process JPA query + Time taken to build response is the total time taken by olingo. We try to tune the JPA queries using Query hints, but still build response time is also very large. I have a question : Is there any way we can reduce the time taken to build the response ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
