Skip to content
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

Class 65k tests is disproportionally slow #3516

Open
nohwnd opened this issue Mar 24, 2022 · 1 comment
Open

Class 65k tests is disproportionally slow #3516

nohwnd opened this issue Mar 24, 2022 · 1 comment

Comments

@nohwnd
Copy link
Member

nohwnd commented Mar 24, 2022

Creating a class with 65k tests (limit of max methods per class is just a smidge above that), results in the run being really slow.

Class with 10k empty tests runs in about 4 seconds. (Even if there are 9999 filters).

Class with 65k tests run over 4 minutes.

This does not seem to be related to filtering, it takes this long even without any filters applied.

I did not check if this happens if the total amount of tests are over a given limit. Single class with more than 10k tests is unlikely, but run with 20k tests in total is not as unlikely.

AB#1865125

@nohwnd
Copy link
Member Author

nohwnd commented Aug 3, 2023

Added to sprint for quick test if someone can see what is going on. We mostly should optimize for test runs of 1-100 tests, and discovery of 10-1000 tests, so this is quite a bit out of that scope, but still might be worth it if obvious problem is found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant