Unset() != free() is the bummer in the CLI env. :-( Def could use that to help shape the performance contour in a daemon env since the "request" never ends unless you self-terminate. Even then it can be tricky to get that lifetime right if your loads change, etc.
-- AD > "leak", which honestly surprised me. We even explicitly unset the vars > but that doesn't guarantee the GC kicks off for them near-time? > > unset() != free(). The memory allocated is still freed during > the request shutdown (where GC actually kicks in). > > As a total aside, and being a paranoid C++ guy, I would love a "free" > method that I could call that frees what I tell it to exactly when I > tell it to... :-) > > I think someone requested this before but it was shut down for > some reason..can't remember what it was again. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
