[
https://issues.jboss.org/browse/TEIID-5583?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5583:
---------------------------------------
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.
Generally you do not need to adjust the heap for materialization. Only page metadata and
the table structures are held in heap memory - the actual data pages are pushed to lower
storage tiers as necessary.
From the linked case it should first be determined what is holding the
memory that is causing the OOM exception.
> 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)