Stephan

The config is more or less the default. Setting debug false/true doesn't make a difference ```

Alright, I figured out what is causing this. If I fully remove ``` includes: - vendor/staabm/phpstan-dba/config/dba.neon ``` and only configure this one service ``` services: - class: staabm\PHPStanDba\Ast\PreviousConnectingVisitor tags: -...

Apologies, somehow I missed the second PR this morning. Unfortunately, no improvements. | |php ./bin/phpstan|php -d zend.enable_gc=0 ./bin/phpstan| |----|--------|-----------------| |0.2.8.1|9:04.60| 3:01.07| |less-parents |13:31.71| 2:57.27 | |less-previous |9:20.37|3:00.74| |less-both |14:04.19|2:56.77|

So, I have been looking into this a bit. Looks like most profilers just tell you which method/function leaks the memory but not which objects are leaked. The one profiler...

I confirm this is still an issue with PHPStan 2.x. The changes in #729 definitely help quite a bit and reduce the overhead by more than 50% | |php ./bin/phpstan|php...

Nice another win! Running PHPStan with `dev-weak fa8541a` brings the time down to `3min34s`. Time with garbage collection disabled stays the same.

No improvements, but on the bright side, it looks like all/most of the overhead is now coming from elsewhere. | |php ./bin/phpstan|php -d zend.enable_gc=0 ./bin/phpstan| |----|--------|-----------------| |0.3.33| 3min28s | 2min38s...

Thank you for looking into this already. I run latest stable and this branch with GC enabled and disabled. Looks like there is a slight improvement when gc is disabled....