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
The text was updated successfully, but these errors were encountered:
powersjcb
changed the title
Default worker configs result in huge slow-down in linting
Default worker configs result in huge slow-down when running esprint check
Oct 2, 2020
Anyone have any clues why there is such a small performance improvement on this project from changing the number of worker at the low end?
My initial thought is that there would be close to a doubling of performance when adding the first few workers. :-\
$ time esprint --workers=1 check
esprint --workers=1 check 0.62s user 0.12s system 5% cpu 14.778 total
$ time esprint --workers=1 check
esprint --workers=1 check 0.66s user 0.12s system 5% cpu 15.227 total
$ time esprint --workers=1 check
esprint --workers=1 check 0.68s user 0.13s system 5% cpu 15.402 total
$ time esprint --workers=2 check
esprint --workers=2 check 0.67s user 0.13s system 5% cpu 13.913 total
$ time esprint --workers=2 check
esprint --workers=2 check 0.65s user 0.13s system 5% cpu 14.041 total
time esprint --workers=3 check
esprint --workers=3 check 0.65s user 0.14s system 5% cpu 14.136 total
$ time esprint --workers=3 check
esprint --workers=3 check 0.65s user 0.13s system 5% cpu 14.062 total
According to my inspection of the execution process, I had a huge performance loss because the startup of the eslint engine takes a good amount of time, not really the linting process.
For example, I'm using the typescript parser on lint but when it's used on multiple workers, the initilization of the typescript watcher takes a HUGE amount of time.
Followup based on what's referenced in the ticket #122
Using the default number of workers on a MacBook pro results in the system grinding to a halt. 100% CPU/Memory utilization for a ~10k LOC project.
With defaults:
With
--workers=2
:Environment:
The text was updated successfully, but these errors were encountered: