comment on

Unfortunately, the relatively simple tests I benchmarked weren't "a little slower". They were 7x slower!

Ouch! I can see how that it would be disastrous to expend all the effort of converting only to find those monsters running like they were on 1990's hardware :)

Thanks again for an incredibly educational and fun (and frustrating... but not due to you) conversation!

As always with the interesting problems. I probably got as much out of the exercise as you did. That's what keeps me coming back to this place. Moi petites cellules grises need stimulation otherwise they atrophy. Fast!

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

RIP an inspiration; A true Folk's Guy

In reply to Re^18: Memory leak question by BrowserUk
in thread Memory leak question by SBECK

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks