[seam-dev] Seam Startup Performance

Pete Muir pmuir at redhat.com
Sun Jul 10 13:47:11 EDT 2011


Mark, I don't think we can make this the default in 1.1 as it breaks backwards compatibility completely. However we could add a spec'd option to enable this. WDYT? If you like this idea please raise on cdi-dev.

On 9 Jul 2011, at 13:40, Mark Struberg wrote:

> Folks, what if we step back and fix the CORE of this disaster?
> 
> Lets not pickup non CDI scope annotated beans as @Dependent automatically anymore! 
> 
> We could automatically enable this feature if we detect a version="1.1" in beans.xml. This way we can keep backward compatibility
> 
> LieGrue,
> strub
> 
> --- On Fri, 7/8/11, Dan Allen <dan.j.allen at gmail.com> wrote:
> 
> From: Dan Allen <dan.j.allen at gmail.com>
> Subject: Re: [seam-dev] Seam Startup Performance
> To: "Stuart Douglas" <stuart.w.douglas at gmail.com>
> Cc: "Seam Dev List" <seam-dev at lists.jboss.org>
> Date: Friday, July 8, 2011, 11:45 PM
> 
> On Fri, Jul 8, 2011 at 19:27, Stuart Douglas <stuart.w.douglas at gmail.com> wrote:
> 
> 
> Hi Guys,
> 
> 
> 
> I was just looking at the startup performance of the Seam 3 booking example on AS7, and I noticed that because the Seam 2 archives that it deploys are bean archives, it actually wastes quite a lot of time on startup registering Seam 3 classes as CDI beans that are never used.
> 
> 
> 
> 
> 
> It occurred to me that we can get around this by using a beans.xml that includes welds <scan> extension in beans.xml to prevent uneeded beans being registered we could significantly improve the performance and memory usage of Seam 3 apps.
> 
> 
> 
> Now that the ridiculous visibility and extensions in non-bean archive problems are resolved, I'm in favor of switching back to registering beans manually rather than using beans.xml. That seems like a performance enhancement that's portable, so that we don't suck if Weld isn't the provider.
> 
> 
> But I agree we should do one of the two options. We'll be moving tests around in Seam to align the setup, so it seems like a good time to run tests with the updated bean registration strategy.
> 
> 
> -Dan
> -- 
> Dan AllenPrincipal Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
> 
> http://www.google.com/profiles/dan.j.allen#about
> 
> 
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> 
> 
> 
> -----Inline Attachment Follows-----
> 
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
> 
> 
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev




More information about the seam-dev mailing list