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

FCS performance benchmark notebook #11802

Closed
TIHan opened this issue Jul 8, 2021 · 4 comments
Closed

FCS performance benchmark notebook #11802

TIHan opened this issue Jul 8, 2021 · 4 comments
Labels
Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. Theme-Performance

Comments

@TIHan
Copy link
Member

TIHan commented Jul 8, 2021

Implement automation of FCS benchmarks

Effectively, we need to quantitatively measure the impact of our performance improvements.

@TIHan TIHan added the Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. label Jul 8, 2021
@TIHan TIHan mentioned this issue Aug 4, 2021
8 tasks
@jonsequitur jonsequitur changed the title Automate FCS benchmarks FCS performance benchmark notebook Oct 7, 2021
@nojaf
Copy link
Contributor

nojaf commented Oct 12, 2021

Are these benchmarks somewhere public?

@TIHan
Copy link
Member Author

TIHan commented Oct 12, 2021

Yes.
https://github.com/dotnet/fsharp/tree/main/tests/benchmarks/BenchmarkComparison
dotnet/performance#2027

@auduchinok
Copy link
Member

@TIHan Is it possible to see the history of how this benchmark changes? Maybe, there's some public graph that's updated periodically?

@vzarytovskii
Copy link
Member

@TIHan Is it possible to see the history of how this benchmark changes? Maybe, there's some public graph that's updated periodically?

Yes, we do want to have plans to have it running periodically and publish the data. I will be creating a bunch of issues for that soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. Theme-Performance
Projects
None yet
Development

No branches or pull requests

5 participants