[
https://issues.jboss.org/browse/TEIID-5500?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5500:
-------------------------------------
Hopefully to update the server-ext framework for this should not be too much work.
Originally I did not pursue this because we were always working with a small batch size of
256 which is default, so EntityCollection size of limited in terms of memory exhaustion.
But having the "chunked" response is the key thing here for managing the client
side of the equation, which I did not consider before. But I do think Olingo supports the
inflight parsing on the client side, which is not necessarily a concern from Teiid point
of view.
Improve OData performance
-------------------------
Key: TEIID-5500
URL:
https://issues.jboss.org/browse/TEIID-5500
Project: Teiid
Issue Type: Enhancement
Components: OData, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.2
See
https://developer.jboss.org/thread/277783
There is a significant overhead for OData vs. JDBC for a single client especially in
terms of latency.
We should investigate pre-building additional batch results and entity caching in
general.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)