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

Ideas for reducing the time required to run all benchmarks #78

Closed
adamsitnik opened this issue Jun 29, 2018 · 1 comment
Closed

Ideas for reducing the time required to run all benchmarks #78

adamsitnik opened this issue Jun 29, 2018 · 1 comment

Comments

@adamsitnik
Copy link
Member

adamsitnik commented Jun 29, 2018

@jorive I am going to add all the ideas I have here and one day we can start the improvements from here.

  1. PingPong benchmark from System.Threading.Channels.Tests takes 2.5s to execute. It's executed for 3 channels, up to 20 times for each of them. 2.5 x 3 x 20 = 150 seconds. The solution would be to change the inner iteration count from 1_000_000 to 1_000 or any other smaller value. fixed in Remove inner iteration counts from the benchmarks #126
@adamsitnik
Copy link
Member Author

Another idea: introduce "Priority" categories. Example: we have benchmarks for non-generic collections, which should not be used by the people who care about performance. We can run those tests only before a major release, not with every CI urn

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

No branches or pull requests

2 participants