[teiid-issues] [JBoss JIRA] (TEIID-5007) Changes to reduce Teiid in the cloud footprint

Steven Hawkins (JIRA) issues at jboss.org
Mon Aug 21 20:17:00 EDT 2017


    [ https://issues.jboss.org/browse/TEIID-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452186#comment-13452186 ] 

Steven Hawkins commented on TEIID-5007:
---------------------------------------

Made a commit to move saxon dependencies our of core classes, such as the Evaluator and Validator.  That dependency as well as xom and nux can be left out of the runtime without error as long as xml functionality is not used.  This can be abstracted further if need in a separate module.

> 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.x
>
>
> 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.2.3#72005)


More information about the teiid-issues mailing list