-
-
Notifications
You must be signed in to change notification settings - Fork 776
BenchmarkDotNet profiler #898
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
BenchmarkDotNet profiler #898
Conversation
|
How's this PR doing? |
|
Hey @clairernovotny, so the profiler project is basically ready, but as mentioned above I can't get the Any help here? 😅 |
|
A lot has changed in Refit since 2020, including its use of Source Generators. A profiling project would still be most welcome if anyone cares to finish this! :) |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What kind of change does this PR introduce?
This PR adds a profiler project using
BenchmarkDotNet.What is the current behavior?
There is no built-in profiler.
What is the new behavior?
There is a profiler to benchmark some REST calls on .NET Core 2.1 and 3.1.
What might this PR break?
Nothing.
Please check if the PR fulfills these requirements
Other information:
cc. @clairernovotny, this PR is still marked as draft for now. I can't figure out how to make the project build with
BenchmarkDotNetwhenrefitis directly referenced from the local projects and not through NuGet, could you help with that? I copied/modified the.csprojcode from the test project and I can get the profiler to build and run correctly if I run it directly from VS and try to execute one of the benchmarking methods, but if I use justdotnet Refit.Profiler.dlland letBenchmarkDotNetdo its thing, it fails to run the benchmark with an error saying the interface in use is not a validrefitinterface, which shows the build task is not run correctly I guess? Any help here is welcome 😄cc. @Dreamescaper - feel free to help out with new benchmarks to add!
NOTE: this PR needs to be merged in before #897 so that we can then run comparative benchmarks between the two versions of
refitin that other branch before adding those optimizations.