You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've done some - not entirely scientific - benchmark checks and am finding that enabling the caching option when on Windows (not sure about other OSes), makes a CS run significantly slower.
For a CS run with a custom ruleset and the following command over 57 files:
Expected behavior
I would expect a little bit of a slow-down the first time PHPCS is run with cache turned on as the cache file needs to be written, but the slow-down I'm seeing now is out of bounds.
Versions (please complete the following information):
OS: Windows 10
PHP: 8.1.2
PHPCS: master, but also checked 3.6.2 tag
Standard: custom
Additional context
I haven't done a git bisect yet to figure out if I can pinpoint the slow-down to a specific commit, but felt that the time difference is so huge and on the negative for having caching turned on, this had to be reported forthwith.
The text was updated successfully, but these errors were encountered:
Describe the bug
I've done some - not entirely scientific - benchmark checks and am finding that enabling the caching option when on Windows (not sure about other OSes), makes a CS run significantly slower.
For a CS run with a custom ruleset and the following command over 57 files:
These are the approximate timings I'm seeing:
--no-cache
)master
Expected behavior
I would expect a little bit of a slow-down the first time PHPCS is run with cache turned on as the cache file needs to be written, but the slow-down I'm seeing now is out of bounds.
Versions (please complete the following information):
master
, but also checked3.6.2
tagAdditional context
I haven't done a
git bisect
yet to figure out if I can pinpoint the slow-down to a specific commit, but felt that the time difference is so huge and on the negative for having caching turned on, this had to be reported forthwith.The text was updated successfully, but these errors were encountered: