Performance regression in 8.0.0
See original GitHub issueWhen I upgraded from 7.0.1 to 8.0.0, linting my project started taking 2.5x as long as before.
git bisect
says:
6fe21e6e96f479d63055cda50d341b1142f7b8ec is the first bad commit
commit 6fe21e6e96f479d63055cda50d341b1142f7b8ec
Author: Mathias Schreck <schreck.mathias@googlemail.com>
Date: Mon Aug 3 13:38:11 2020 +0200
Improve data structure of custom names
README.md | 24 +----
lib/rules/no-exclusive-tests.js | 2 +-
lib/rules/no-skipped-tests.js | 2 +-
lib/util/ast.js | 14 +--
lib/util/names.js | 164 +++++++++++++++++++++------------
lib/util/settings.js | 24 +----
test/rules/max-top-level-suites.js | 8 +-
test/rules/no-async-describe.js | 2 +-
test/rules/no-exclusive-tests.js | 22 ++---
test/rules/no-hooks-for-single-case.js | 8 +-
test/rules/no-identical-title.js | 8 +-
test/rules/no-nested-tests.js | 8 +-
test/rules/no-setup-in-describe.js | 26 ++----
test/rules/no-sibling-hooks.js | 8 +-
test/rules/no-skipped-tests.js | 23 +++--
test/rules/no-top-level-hooks.js | 4 +-
test/rules/prefer-arrow-callback.js | 1 -
test/util/namesSpec.js | 151 ++++++++++++++----------------
18 files changed, 244 insertions(+), 255 deletions(-)
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Major performance regression from 6.10.2 to 7.x and 8.0.0-test
I'm seeing a major performance regression from Node 6.x (e.g. 6.10.2) to all versions of Node 7.x and v8.0.0-test20170511830c4bf319. The ...
Read more >TensorRT 8.4.1 Release Notes - NVIDIA Documentation Center
There is an up to 7.5% performance regression compared to TensorRT 8.0.1.6 on NVIDIA Jetson AGX Xavier™ for ResNeXt networks in FP16 mode....
Read more >[10/11/12/13 regression] 20% slowdown of linux kernel AES ...
I ran the testcase in comment #7 and can confirm that there is a 5.24% performance regression from 6.3.1 to 7.2.1, and a...
Read more >Changes in MySQL 8.0.28 (2022-01-18, General Availability)
The change just described represents a regression; the problem is better solved by deriving a more precise resolved data type, ...
Read more >Prism 8.0.1 Release Notes - GraphPad
When normalizing, added a new option to define 100% of each column as the average of all values in that column · Multiple...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
7.0.0
8.0.0
8.1.0
Thanks for reporting this. My initial assumption is that the refactoring of
astUtils
is causing this, because now they are wrapped in a function an called for every rule and every linted file. I was planning to rewriteastUtils
anyway to address a couple of other issues, so I hope that I can improve the performance along the way. Anyway the first step should be implementing a performance regression test, that will fail when the performance decreases.