Cpu usage goes higher and higher about resource-watcher HOT 4 CLOSED

Blackfire suggests that the ExcludeDirectoryFilterIterator might be the culprit here.

I created a simple test script based on your example: https://gist.github.com/colinodell/d6fd7a4cb6d9fbf8aa20154755278385

I ran this script with 50 iterations and again with 200 - a 300% increase. I expected to see a corresponding 300% increase in CPU usage; however, I saw a 466% increase (1.65 seconds to 9.31 seconds):

This iterator is used to exclude certain files; by default, the Finder will exclude dotfiles and VCS files. On a hunch, I added these two calls to the Finder configuration:

  ->ignoreDotFiles(false)
  ->ignoreVCS(false)

I then re-profiled and got these results which matched the ~300% increase I expected:

CPU time went from 887ms to 3.35 seconds.

from resource-watcher.

@colinodell Thank you so much for the your input here. I added

  ->ignoreDotFiles(false)
  ->ignoreVCS(false)

and the problem seems to have been solved now. So I'm very happy with the suggestion you made.

Something I don't understand well yet is why the cpu kept growing. I'd assume that without the added code the cpu usage should have stayed on the same level. Do you know why the cpu was growing on each iteration?

from resource-watcher.

I'm not really sure why it kept growing.

Time spent in the constructor grew by 10x:

According to Blackfire, most of that extra time came from the constructor itself, not other function calls:

Perhaps there's something going on at the language/interpreter level? Maybe extra garbage collection, memory allocation, or something like that? (I don't know - that's beyond my knowledge)

I also saw a bunch of time spent rewinding iterators - not sure if that's also related or not.

from resource-watcher.

Thanks for the response @colinodell

from resource-watcher.