Re:Composer – Disable GC when computing deps and refs
by rossriley on Tuesday December 02, 2014 @09:17AM
(#8687166)
It seems when you start to hit the memory limit PHP's automatic garbage collection will loop through the constructed objects to see if any can be cleaned up.
If none can (and in the case of Composer all the objects exist for a reason) then it's wasting time analysing the objects.
So in this case there's only a large waste of cpu doing nothing with gc enabled.
Re:Composer – Disable GC when computing deps and refs
by icebraining on Tuesday December 02, 2014 @09:21AM
(#8687182)
Well, yes and no, since some of the reports show an increase in memory usage, so the gc was doing something.
Re:Composer – Disable GC when computing deps and refs
by masklinn on Tuesday December 02, 2014 @09:37AM
(#8687265)
Most reports don't show significantly changed memory usage though (some increase slightly, others decrease slightly).
Re:Composer – Disable GC when computing deps and refs
by Alan01252 on Tuesday December 02, 2014 @09:53AM
(#8687360)
The pull request is better:
Re:Composer – Disable GC when computing deps and refs
by derickr on Tuesday December 02, 2014 @09:54AM
(#8687365)
I think the article on this, explains why a memory reduction by garbage collection also increases execution speed: http://derickrethans.nl/collecting-garbage-performance-consi...
Any more details on this?