So the issue is either that the .0004 second improvement in the operation represents more than a 25% optimization (since an actual 25% optimization should result in a linear speed gain), or that the optimization of a single item somehow resulted in a non-linear performance improvement.
That, I can't help you with; perhaps dws is onto something. I couldn't run the benchmark and haven't the time to tweak it and break out "get" versus "set", at the moment. (Nor have I the time to speculate on why it might not be a linear improvement.)
Apparently, I've got just enough time to be no help at all. At least my keen grasp of the obvious is intact.
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! —
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.