[
https://issues.jboss.org/browse/TEIID-5583?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5583.
-----------------------------------
Resolution: Won't Fix
Marking as won't fix for now - until there's a determination of what's needed.
The residual heap memory footprint of a materialized view will be proportional to the
number of rows / working page size - but is generally small enough as to not be a primary
consideration when determining the overall heap. The actual page data will swap to disk
as needed. The rule of thumb from the docs is conservative as to allow for plenty of
working heap space, retaining soft references to index pages, etc.
Provide ability to monitor how much memory matviews are using
-------------------------------------------------------------
Key: TEIID-5583
URL:
https://issues.jboss.org/browse/TEIID-5583
Project: Teiid
Issue Type: Enhancement
Reporter: Colin Mondesir
Assignee: Steven Hawkins
Priority: Major
In the docs it says "Internal materialization (and temp tables in general) have
memory overhead for each page. A rough guideline is that there can be 100 million rows in
all materialized tables across all VDBs for every gigabyte of heap."
But we have no feature that allows us to monitor how exactly how much memory matviews are
actually using, this makes adjusting the heap to match changing requirement difficult.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)