A common approach for increasing performance is just to use caching. In a way, generating static files is one form of caching, but there are others that you could consider, which might be easier than a rewrite of your application from dynamic pages to static pages:

• You can cache at the DBIx::Class level
• You can cache on the Catalyst level (probably requires more code changes, but gives you fine-grained control over what to cache).

• You can cache at the webserver level. For example with Apache, you can use a caching reverse proxy. If the caching rules for your site are easy, this might be the solution with the least code changes.

In any case you can invalidate the whole cache when there are big updates to your database.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.