Well, if you are running on a Windoze box, you could be slamming
the memory ... we'd have to see the code to say for sure, though.
If that is the case, you may be forcing 'doze to use virtual
memory (you know, hard disk) for data structure storage. On
a fragmented drive, that incurs an even greater performance
penalty of course.
Can you update us with details about the platform, data structures,
etc.?
Update from HZ: It has been noted to me (thank
you
tye) that other systems can also penalize you for
slamming memory. In any case, we need more details to help you.
Please, sir, can we see your code?
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.