Well, as it turns out memory caching was not the problem. I proved this by running the first and last test scenario each immediately after a reboot. The timing results were nearly identical to what I got when I ran all seven of my tests one after the other with only a restart of the application between them.
I was however able to figure out a way to clear the windows memory cache from a script. There are some freeware tools that can do this, but they are windows apps with no (useful) command line interface. The one I used was CacheSet from Sysinternals. Then I wrote a little wrapper module that calls this using Win32::GuiTest. Kinda kludgy, but it got the job done.
At least I learned a new Perl Module.
--DrWhy
"If God had meant for us to think for ourselves he would have given us brains. Oh, wait..."
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.