On Aug 16, 2006, at 5:08 PM, Michael Peters wrote:
A memory leak is when memory is used and then lost and can't be recovered. If the process can still access or use that memory, it's not a leak, it's just memory growth. Leaks should be completely eliminated. Growth should be managed.
I don't know if my problem is growth or leak or what. I do know that 1000 requests to a single URL , which renders essentially static content , grows several megabytes, it needs to be addressed. Could it be growth? Sure. Could it be a leak on the perl integration? Sure- but doubtfully.
What i do know is that somehow some variables, somewhere (i'm guessing anon hashes ) are not getting cleaned up when they should be. I can either spend a few hours fixing that now, or leave it as- is and support it. i used to work at a place that did countless hack jobs with no QA and tons of bugs, because they made the cash on support & maintenance (clients didn't care, because they had something online in 2 weeks instead of 4 months). I HATED , beyond belief, dealing with that stuff.
if there's an issue, big or small, i want to know where it is. if i can fix it-- great. if i can't fix it, i can document what the issue is, so maybe i can fix it when able to or when something goes wrong, i know where to look.
