<div dir="ltr"><div class="gmail_default" style="font-size:large">One thing I would like to mention is that with our OpenShift first strategy, anything we do should also take into account memory footprint changes.</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">We are still doing analysis on the memory footprint of EAP, but will have something to publish fairly soon. </div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">One thing we should avoid here is approaches that allocate memory that won't go away when the boot process is done.</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">Andy</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 16, 2017 at 7:47 AM, Jason Greene <span dir="ltr"><<a href="mailto:jason.greene@redhat.com" target="_blank">jason.greene@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><span class=""><br><div><blockquote type="cite"><div>On May 16, 2017, at 7:41 AM, Heiko Braun <<a href="mailto:hbraun@redhat.com" target="_blank">hbraun@redhat.com</a>> wrote:</div><br class="m_-1737917536123910823Apple-interchange-newline"><div><div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>On 16. May 2017, at 13:32, J Pai <<a href="mailto:jai.forums2013@gmail.com" target="_blank">jai.forums2013@gmail.com</a>> wrote:</div><br class="m_-1737917536123910823Apple-interchange-newline"><div><span style="font-family:Helvetica;font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">What I have experienced is that for end users, they are mostly interested in seeing their (usually large) deployments show noticeable improvements in deployment time, not necessarily from a cold boot of the server, but when the server is already up and they either want to deploy something new or re-deploy their application.</span><br style="font-family:Helvetica;font-size:16px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"></div></blockquote><br></div><div>+1 the deployments increase the time until “ready to perform work”. This is the point we should use as a reference. Anything before (i.e. blank WF without deployments) is just marketing IMO.</div></div></div></blockquote><br></div></span><div>I agree that deployment time is important, but I just want to point out that not all usages of WildFly involve deployments. Examples include proxy servers, static content servers, message brokers, javascript code, transaction managers, and service based applications. </div><br><div>
--<br>Jason T. Greene<br>WildFly Lead / JBoss EAP Platform Architect<br>JBoss, a division of Red Hat
</div>
<br></div><br>______________________________<wbr>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div><font size="4">Andrig (Andy) T. Miller<br></font></div><font size="4">Global Platform Director, Middleware<br></font></div><font size="4">Red Hat, Inc.</font><br></div></div></div></div>
</div>