Yes that's basically true although Dmitry can probably elaborate. I believe if the collector kicks in there'll also be a bit of a slowdown but my main concern is to be able to turn it off because of stability. As you can see with the update patch it seems performance is quite good. Anyway will circle back with Dmitry just to be sure.
Andi > -----Original Message----- > From: Derick Rethans [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 05, 2007 3:10 PM > To: Stas Malyshev > Cc: Andi Gutmans; Guilherme Blanco; [EMAIL PROTECTED]; Rasmus > Lerdorf; Antony Dovgal; Cristian Rodriguez; internals@lists.php.net > Subject: Re: [PHP-DEV] Garbage collector patch > > On Wed, 5 Dec 2007, Stanislav Malyshev wrote: > > > > > To clarify I meant there's a tri-state (not compiled in, compiled > in but > > > > collection turned off, compiled in but collection turned on). My > > > > recommendation was to always compile it in but to keep collection > turned > > > > off by default. > > > > Do I understand it right that being compiled in, "turned on" and > "turned off" > > have the same performance implications (slightly slower, a little bit > more > > memory) and the difference is mainly stability-wise? > > Yeah - atleast, that's how David's original patch behaved. > > regards, > Derick > > -- > Derick Rethans > http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
