Perrin Harkins wrote:
On 3/9/07, Bill Moseley <[EMAIL PROTECTED]> wrote:
I just checked and on some pages I'm calling uri_for a few hundred
times. If that's a bottle neck then optimization would be most
welcome.
I'm sure it depends on your usage, but for Jim Spath it was only about
4% of his time. It would help, but you probably won't be able to see
the difference.
- Perrin
You are correct Perrin. I removed all uri_for() calls from our
templates, and there wasn't really a noticable difference.
Some things that did help were figuring out that we were only utilizing
1 of our 2 memcached servers (whoops!) and using
Catalyst::Plugin::Compress::Deflate. While these two items don't really
address any performance issues that are due to Catalyst itself, they
significantly increased our requests/second in ab.
At this point, besides optimizing the code itself, I am really only left
with template caching, and prebuilding localized templates.
We also investigated using ClearSilver for our templates, but
ClearSilver seg faulted when we passed it complex data structures in the
stash.
Anyways, thanks for all the feedback! It's been very helpful.
- Jim
_______________________________________________
List: [email protected]
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
