I am reminded of the original development of RISC machines.
Those guys found that the only way to find the "best"
approach was to take a sufficiently large example set (booting
UNIX and running some programs) and run it in a well
When someone proposed a change to the architecture they
changed the simulation, measured the effect on performance
and kept it if it improved the situation.
My guess would be (based admittedly on a total lack of
first hand knowledge) that adding metrics to Parrot (or
Perl 5?) that
emulated the effect of fetching information from disk/ RAM/
cache would lead to a reasonable simulation of Perl's
performace and hence could definitively answer these type
This would allow anyone with enough interest and time
on their hands to get a real answer rather than just
sticking a wet finger in the air.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||