It is worth keeping in mind that perl's test suite is not designed for benchmarking, and probably spends the majority of its time doing things very unrepresentative of any kind of normal workload. So while these timings may give a rough indication which build options are likely to be faster, any specific real workload will have its own unique set of timings which are unlikely to map closely to these figures.

For one $work application a few years ago, we came up with a figure of about 25% speedup for a perl built without threads, for example. (That was probably around perl-5.18.) There's really no substitute for testing things on your own workload (which I think @Tux was saying, but not sure the message got through :).

---

---

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.