* On Sat, Feb 21 2009, Oleg Pronin wrote: > I use Catalyst in extremely loaded projects (currently 60.000.000 pageloads / > day). > Thereforce i'm perfomance paranoid man. > > One of 'black stones' is the ->config method. It has dramatically slow > perfomance at > config_method: 1 wallclock secs ( 1.06 usr + 0.00 sys = 1.06 CPU) @ > 3808.94/s (n= > 4047)
I have to ask... is this actually slowing down your application? Let's say that your app spends 1% of its time in $c->config. If you made $c->config 10000x faster, you would only make your app 1% faster. > It would be VERY GREAT if we somehow make ->config works a hundred > times faster because everybody use ->config without any suspicions on > its speed. Although I haven't noticed config calls slowing down my application, I look forward to seeing your patch for this. FWIW, I usually only call $c->config at app startup time; I read it and pass values in it as arguments to other classes that need configuration information. I'm pretty sure this is the intended use; you shouldn't be looking in it during requests. Regards, Jonathan Rockway -- print just => another => perl => hacker => if $,=$" _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/