Scaling up the load of your normal tests will show if your
code "works" in a pragmatic sense. That is difficult in your case or you have undisclosed motives.
Using Devel::Cover could verify that your caching code is being exercised.
If your cache is implemented with a call tree, i.e.
sub fetch {
return _cached_fetch($_[1]) if _cached( $_[1] );
return _via_normal_retrieval( $_[1] );
}
there are packages that will insert code at the entry or
exit of a set of routines. This would let you insert a logging function
into
fetch and
_cached_fetch to generate statistics on cache performance. I cannot think of the name for this type of function modification.
The insert code could be something like
sub log_cache {
local $, = " ";
print SOMEWHERE "MyObj cache called", caller(1), "w/",$_[1],$/;
}
cleaned up for log readability.
Be well,
rir
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.