Ted Pedersen wrote on 10/22/09 7:14 AM: > I'm very much of the school of thought that says when using Perl you > should just to things "the Perl way" and not try to optimize memory > use too much (avoiding obvious mistakes is about the best you can do), > just because the benefits of Perl are to a large extent paid for by a > ton of memory use. It's horrible really. :) But, the advantages of > Perl are (for me) often enough to make the cost in memory bearable.
agreed. I usually optimize for developer time, which is the single most expensive component. :) [snip] > also grows. But how much? I'm not sure of that. So, last night I set > up some runs of NSP in one window and I watched 'top' in the other. :) > It wasn't ideal, because from time to time I'd get bored and miss when > a program finished. :) Hence my quest for a memory profiling too - to > save me from getting bleary eyed staring at top output. Anyway, I'll > be sending some results of that little experiment to the NSP list > later today I think. The news isn't all bad actually - expensive, but > not exponentially so. there's a related thread here: http://london.pm.org/pipermail/london.pm/Week-of-Mon-20060130/001126.html which you may have already found. -- Peter Karman . http://peknet.com/ . [email protected]
