[
https://issues.jboss.org/browse/TEIID-5500?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5500:
---------------------------------------
But having the "chunked" response is the key thing here for
managing the client side of the equation, which I did not consider before.
The concern is still over the requested page size. As long as it's "small"
it makes little difference whether we build an entity set 256 at a time or iteratively.
The chunking is a lower level resultset/caching concern. However if someone sets or
requests a larger page size, then problems could arise - which we could just limit the
page size or implement this streaming style result.
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)