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

[Steven Hawkins (JIRA)]

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

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

> The default standalone.xml in Openshift image is stanndalone-openshift.xml file, see if there are config information.

Yes, that does have the changes for KUBE PING.  I missed that on a first glance.  Thanks.

> Also, see in JDG shared cache service configuration, that is based on WildFly too, they must be clustered JGroups there too.

>From what I have seen the JDG/infinispan clustering configures a jgroups specifically for infinispan.

> 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)