[
https://issues.jboss.org/browse/TEIID-219?page=com.atlassian.jira.plugin....
]
Steven Hawkins commented on TEIID-219:
--------------------------------------
We do now have active restrictions on memory / disk, but not proactive restrictions.
Possible Dimensions:
- cpu
- memory (max footprint / total usage)
- network (from a source, all sources, to client)
- wall clock time - active restriction based upon timeouts
With the current logic we are best suited to estimate memory / network based upon row
counts. There again we have an active, but not proactive restrictions, on source row
counts.
We don't have anything meaningful for cpu utilization as we don't have a model of
consumption down to the expression level. We will likely need to introduce a very simple
metric.
I don't see us making any meaningful estimate of wall clock time.
Add a way to limit or suppress queries that exceed a threshold
Cost-Based Optimizer value
-----------------------------------------------------------------------------------------
Key: TEIID-219
URL:
https://issues.jboss.org/browse/TEIID-219
Project: Teiid
Issue Type: Feature Request
Components: Query Engine, Server
Affects Versions: 6.0.0
Reporter: Marc Shirley
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.0
Client requesting an ability to impose a limit on, or suppress, any query that exceeds a
cost estimate value specified by the user/administrator.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)