-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Added Benchmark Harness (#1729) #1729
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
Conversation
|
A few things to point out.
|
| }); | ||
| } | ||
|
|
||
| [Benchmark] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if there is any penalty having the xunit fact in this file. I imagine that harness file getting pretty large
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because it's xUnit and it should simply run all [Fact] in the project, we should be able to break up the harness files into smaller files in the future as needed.
| } | ||
|
|
||
| [Fact] | ||
| public void Reactive_List_Operation_Benchmark() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add my bench marks for the inpc property observable in the framework. In the pr I linked the other day.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added.
- Added NavigationStack Benchmarks - Added AutoPersist Benchmarks - Added ReactiveList Operations Benchmarks - Added RoutableViewModelMixin Benchmarks
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Resolves #1711
Resolves #1276
What is the current behavior? (You can also link to an open issue here)
There are no performance tests
What is the new behavior (if this is a feature change)?
Adds a harness for ReactiveUI to execute performance benchmarks
What might this PR break?
Nothing. This PR is additive. Nothing in this PR affects the core solution.
Please check if the PR fulfills these requirements