On 29/04/10 19:06, Oleg Pronin wrote:
Maybe it is not the bottleneck, but how many places do we have
like this that are "not a bottleneck" ? maybe the sum of all these
"mini" mistakes is the bottleneck ?
Hi Oleg,
Do you have an application which *has* a bottleneck at the moment? If
so, can you demonstrate it?
Quite a lot of people on this list are trying to tell you that Catalyst
runs some very big sites quite successfully, and my own experience backs
that up.
Whenever I've hit a bottleneck in a site, it has turned out to be:
* Database calls (usually with expensive queries)
* Poorly designed TT templates
* Stupid blocking calls in a controller (eg. sleep, system, waitpid, etc)
* Network bandwidth
But NOT the speed of accessor methods in Catalyst. They really are not
an issue.
If you *do* have a performance issue yourself, then please feel free to
bring up a specific example, but otherwise, quit worrying.
If you are concerned that you're not squeezing the absolute most
performance out of every clock cycle on your CPU, then you should go
back to coding in raw assembler instead of Perl, but it's not worth
hassling us about.
Cheers,
Toby
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
