in reply to Re: A (memory) poor man's hash
in thread A (memory) poor man's <strike>hash</strike> lookup table.
I still find hashes a little daunting.
BrowserUK (if I may presume) was speaking in relative terms. Hashes are quite easy compared to (for example) Perl's advanced data structures, object system, or closures.
While hashes may have a tendancy to soak up a lot of memory, it's not using it for that long.
The problem is that perl usually doesn't free the memory back to the OS until the process exits (though it will reuse that memory for other things). This is particularly a problem for mod_perl, where the process will stick around as long as Apache is up (potentially years, if your sysadmin is neglegent about security patches ;).
----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer
: () { :|:& };:
Note: All code is untested, unless otherwise stated
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Re: Re: A (memory) poor man's hash
by liz (Monsignor) on Nov 22, 2003 at 10:29 UTC | |
Re: Re: Re: A (memory) poor man's hash
by etcshadow (Priest) on Nov 22, 2003 at 03:52 UTC |