-
Notifications
You must be signed in to change notification settings - Fork 779
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Axe reporter is very slow with large datasets #512
Labels
Comments
Fixed by #568, provided the implementation uses the new 'resultTypes' options (see PR). |
isner
added a commit
that referenced
this issue
Oct 13, 2017
WilcoFiers
pushed a commit
that referenced
this issue
Oct 18, 2017
mrtnvh
pushed a commit
to mrtnvh/axe-core
that referenced
this issue
Nov 24, 2023
…erjs/tests/example (dequelabs#512) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On extremely large pages, it is possible for the reporter to take several times longer than the actual audit to complete. The main problem appears to be in
helpers.processAggregate()
. Running it 30 000 times took several minutes to complete. Part of the issue here is that the extension is hugely inefficient here because it's processing passes, which won't actually get displayed.Part of the solution should be in preventing that. But there's certainly an extra problem. The method doesn't (or at least shouldn't) do anything that's particularly slow, so we need to figure out what's so slow and we should fix it.
This problem can be reproduced on the following page:
https://dev.office.com/fabric#/components/detailslist
The text was updated successfully, but these errors were encountered: