← Feed

Posts

• Post #4485507

  running different #PHPStan versions on #shopware 6 2.1.43: 1m 33s - takes 8.79GB memory 2.2.8: 1m 25s - takes 7,46 GB memory

• Post #4483540

  Anyone out there with a open source codebase, running #phpstan in CI takes more than 5 minutes? I would love looking into what makes it slow for you Send me a link to your CI logs RT

• Post #4417128

  @OndrejMirtes@phpc.social handed me over a list of #php-src commits to verify and contribute to the php runtime. So I started opening pull requests on the php project to improve performance of #phpstan. Lets see how it goes - wish me luck :-)

• Post #4351038

  Last week I had an idea on how we can improve efficency when #phpstan needs to work with big unions of constant types (e.g. enum with lots of caes). this had a nice impact on some example of our benchmark suite

• Post #4121039

  Since April 2026 we fixed ~280 issues on #phpstan. We implemented lots of new features and improvements along the way and made it even faster at the same time. be prepared for the next release which will do another big leap in #performance 🚀

• Post #3952794

  In case you think #phpstan is running too slow, have a look at the result of running `phpstan analyze` command with `-vv` and check whether it utilizes the result cache When the result cache is warm, it should be wicked fast in CI you likely need to persist the cache manually see https://phpstan.org/user-guide/result-cache#setup-in-continuous-integration

• Post #3788103

  #phpstan 2.2.3+ is able to detect package updates based on composer.lock. utilizing the pre-existing dependency graph, we need to re-analyze only affected files. Previously we had todo a full project analysis. contributed by @sander_scode

• Post #3757194

  We have a few really cool perf experiments running atm to get #phpstan even faster.. some of them look really promising. 🫰

• Post #3664861

  contributed to #phpstan by @zonuexe@phpc.social: PHPStan will have a better idea about purity of callables taking a callback argument. for example will `array_map($pureCb, $arr)` be considered pure: - less false positives - better dead code detection

• Post #2500120

  @OndrejMirtes had another great idea to speedup #phpstan analysis Implementing it was easier than expected :-)

• Post #789627

  In case your daily #phpstan run takes minutes instead of seconds you likely don’t utilize the result cache. Find solutions at https://staabm.github.io/2023/10/21/phpstan-result-cache-gotchas.html

• Post #789625

  Recently I learned that the order in which you pass options to a CLI command can have a huge perf impact on the runtime (even if it leads the same result)

• Post #789624

  dumdidum.. 🚀 #phpstan

• Post #789622

  yesterdays #phpstan 2.1.43 release fixes 37 issues. this means since 2.1.40 (released ~4 weeks ago) we fixed ~195 issues. fingers crossed we can keep the pace and reach our goal of pushing open issues to < 1000 in the upcoming months.

• Post #746811

  my non-scientific benchmark suggests running #PHPStan on #wordpress core, will be a lot faster starting with the next release

• Post #683298

  It was a pleasure to work with @misterdeviling thru a lot of old #PHPStan bugs. Yesterdays release contains a massive package of fixes. while we concentrated on the maintenance parts, @OndrejMirtes could concentrate his efforts on improving DX with better docs and other nice additions.

• Post #606995

  Achievement unlocked: crossed the 1000 commits line in @phpstan core

• Post #450078

  I recently learned that git bisect has a "run" subcommand, which allows you to automate the bisect process. in a blog post I am describing how you can find a regression commit in phpstan-src. the same approach works for any git based project. https://staabm.github.io/2026/02/07/git-bisect-run.html

• Post #450076

  Starting with #phpstan 2.1.39 in case we know constants are deprecated only in certain php versions, we no longer error about them, when used in a `if (PHP_VERSION_ID < 80400) {`-like condition. see E_STRICT before PHP 8.4: https://phpstan.org/r/0dc9fe34-0c60-4254-9174-f37e910cb4cf

• Post #450075

  I love solving puzzles.. today I found out that a #phpstan container cache invalidates when you resize your bash/shell window. also when jumping between directories using `cd`. not intentional of course. lets see what we can do about that.

• Post #450074

  TIL: your github action might fail because of a overlong command line, which gets cut without further notice. Not sure its a #php or #windows or #githubactions effect. 1:1 the same command works on a ubuntu based github action without error

• Post #390509

  After ~6 weeks of collaboration we released a blazing fast #PHPStan version - static analysis on steroids. https://staabm.github.io/2026/01/25/phpstan-on-steroids.html

• Post #390504

  this week I am on vacation from my primary job.. @misterdeviling and me working thru #PHPStan issues and we can look back on a pretty successfull week. Lots of fixed issues and merged contributons. some multi year old bugs fixed. Its a lot of fun

• Post #198995

  @zimzat@mastodon.social not sure what you mean. I have written plenty of extensions without such a problem. Might be specific to a certain extension. If reproducible please file a issue