Re: memory allocation and de-allocation

Yes, my cgi module is still intact, thats on a production server, the commandline version did see a performance hit when I was allocating the array without the fast cache enabled, though normally I'd not go do something silly like roll 26k records into an array I might have to do that sooner or later. I was trying some work based on your intro doc which is what got me into the idea of the php-gtk interface. Nice examples you've got up, very helpfull. Lemme subscribe to the php-dev list and raise this issue brett > On Wed, Mar 13, 2002 at 12:41:02PM +0200, Brett Geer wrote : > > yes indeed, php 4.1.1 > > > > this code idea: > > > > #allocate > > for ($vloop = 0; $vloop <= 200000; $vloop++) > > { > > $varr [$vloop] = "Some arb string to grab some ram..."; > > } > > > > #deallocate > > unset ($varr); > > > > This works quite fine, however an unset on a gui widget does do this, I have > > recompiled php-gtk 0.5.0. > > Possible it just not implemented... > > Anyway .. if this is true for memory allocation, can we say > something about performance loss if you change this > behaviour? > > Why I'm asking is simply exmplained: php in apache and php on > command line are two different worlds. On apache side, it may > be a good idea not to release memory. However, from my point > of view it makes very much sense for the CLI version of PHP > and maybe we should raise this to php-dev@ to discuss certain > things about this aspect there. > > - Markus > > -- > Please always Cc to me when replying to me on the lists. > GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc >