Can you create a small test case that would allow us to profile & optimize this?
On Tue, May 19, 2009 at 2:26 PM, Juanma <[email protected]> wrote: > RaiseHandlerRegistered is called 480 times. That results in 25K calls to > DependencySatisfied, which in turn calls HasValidComponent 53K times. > > Nearly 100% of the time is spent in AbstractHandler.HasValidComponent, with > 50% in DefaultDependencyResolver.CanResolve and 50% in > DefaultKernel.GetHandlers. > > I've attached part of a dotTrace snapshot (in txt format). I can send the > whole snapshot if it helps. > > Thanks. > > > On Tue, May 19, 2009 at 12:03 PM, Ayende Rahien <[email protected]> wrote: > >> Juanma, Can you share what is causing the perf issue in the event? >> A lot of what Castle is doing is done inside that event handler >> >> >> On Tue, May 19, 2009 at 9:19 AM, Juanma <[email protected]> wrote: >> >>> >>> Hi, >>> >>> I have an app which register a lot of componentes (> 500) and >>> performance during container initialization is quite bad. >>> >>> While profiling the app, I've noticed that most of the time is spent >>> in DefaultKernel.RaiseHandlerRegistered. >>> >>> Is there any way to speed up registration? Maybe it's posible to do >>> something like a "batch registration", registering a lot of components >>> and only raising the event after all components have been registered. >>> >>> Thanks in advance. >>> >>> Juanma. >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
