[ https://issues.jboss.org/browse/TEIID-4557?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4557: --------------------------------------- Memory is too loosely defined here. Are we talking about heap, disk, or total. Also the notion of per view doesn't generally make sense as view layers are typically optimized out. If we are talking specifically about materialization, then this could apply to internal. You can currently give a preference on an internal materialized view pages being held in memory, but otherwise we don't currently have limits. I'd consider this a low priority given that global limits could be worked first. I'm assuming this means disk consumption. There's no hard limit on disk consumption on a query/session basis. We currently track by operation (grouping/sort/etc.), which would an easy point to enforce in terms. Tracking on session or query will take more work. It should be noted that there's lots of code that enforces fair resource consumption in terms of heap memory that can be reserved, thread utilization (including time-slicing), etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)