[JBoss JIRA] (TEIID-2684) Unexpected AsynchPositioningException
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2684:
-------------------------------------
Summary: Unexpected AsynchPositioningException
Key: TEIID-2684
URL: https://issues.jboss.org/browse/TEIID-2684
Project: Teiid
Issue Type: Bug
Components: JDBC Driver, Query Engine
Affects Versions: 8.6
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.6
A recent build failed due to an AsynchPositioningException being thrown from TestAsynch.testAsynchPlaning. This is not expected and was reproduced.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2683) Proactive eviction of new batches reduces forward-only performance
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2683?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2683:
----------------------------------
Fix Version/s: 8.6
Description: With TEIID-2429 to improve performance under heavy buffer load the cleaner was made more proactive in evicting new batches. In streaming scenarios this results in a lot of unnecessary buffering as the batches are likely to be held only for a short time.
> Proactive eviction of new batches reduces forward-only performance
> ------------------------------------------------------------------
>
> Key: TEIID-2683
> URL: https://issues.jboss.org/browse/TEIID-2683
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 8.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.6
>
>
> With TEIID-2429 to improve performance under heavy buffer load the cleaner was made more proactive in evicting new batches. In streaming scenarios this results in a lot of unnecessary buffering as the batches are likely to be held only for a short time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months