[teiid-issues] [JBoss JIRA] (TEIID-5007) Changes to reduce Teiid in the cloud footprint
Ramesh Reddy (JIRA)
issues at jboss.org
Tue Nov 21 19:39:00 EST 2017
[ https://issues.jboss.org/browse/TEIID-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492482#comment-13492482 ]
Ramesh Reddy commented on TEIID-5007:
-------------------------------------
so, we need to use same stack as "kubernates" which looks same as in clustered.xml. I am guessing that will work for Teiid.
> Changes to reduce Teiid in the cloud footprint
> ----------------------------------------------
>
> Key: TEIID-5007
> URL: https://issues.jboss.org/browse/TEIID-5007
> Project: Teiid
> Issue Type: Quality Risk
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.1
>
>
> A Teiid instance even as swarm or springboot needs additional considerations to minimize the runtime footprint. This includes:
> * container aware auto-sizing. Detection of the number of cpus and available memory need refined - there are experimental settings being considered for containerized vms to better report these values and there is logic in WildFly and other projects that attempts better auto-detection. We also need to utilize the memory buffer space more and probably as off-heap space (and ideally direct operations on the serialized data)
> * Subsystems required include JTA, webserver, security, which could be satisfied by slimmer alternative versions - especially if we make new assumptions, such as not utilizing xa transactions.
> * Engine dependencies could be application specific - removing xml/xsl support, geometry support, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the teiid-issues
mailing list