3 ms·

Interesting. I was looking at the comments hoping for some more technical background, but unfortunately they seem to have been run over by the animated gif crow

• rossriley 12y ago
  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.
  • icebraining 12y ago
    Well, yes and no, since some of the reports show an increase in memory usage, so the gc was doing something.
    • masklinn 12y ago
      Most reports don't show significantly changed memory usage though (some increase slightly, others decrease slightly).
• Alan01252 12y ago
  The pull request is better: https://github.com/composer/composer/pull/3482 https://github.com/composer/composer/pull/3482
• derickr 12y ago
  I think the article on this, explains why a memory reduction by garbage collection also increases execution speed: http://derickrethans.nl/collecting-garbage-performance-considerations.html http://derickrethans.nl/collecting-garbage-performance-consi...