What kind of profiling have you done? Do you have some hard numbers about bottlenecks? Or have you mostly done thought experiments about where the bottlenecks are likely to be?

Some posts that might be of interest:

• Profiling and Performance - discusses using Devel::Prof to improve performance of a DBI app.
• Profiling perl - lists some alternatives to Devel::Prof
• A profiling surprise ... - discusses ideas for making the database less of an application bottleneck. It includes some links to yet other nodes.
• Optimizing existing Perl code (in practise) - lengthy discussion about the various strategies monks use to optimize their code
• Profiling your code. - Perl Monks tutorial on profiling code

Best, beth

---

---

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.