[wildfly-dev] Speeding up WildFly boot time

Jason Greene jason.greene at redhat.com
Tue May 16 09:47:11 EDT 2017


> On May 16, 2017, at 7:41 AM, Heiko Braun <hbraun at redhat.com> wrote:
> 
> 
>> On 16. May 2017, at 13:32, J Pai <jai.forums2013 at gmail.com <mailto:jai.forums2013 at gmail.com>> wrote:
>> 
>> 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.
> 
> +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.

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. 

--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20170516/2cc47b6c/attachment.html 


More information about the wildfly-dev mailing list