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

Support benchmarking startup performance #335

Closed
cwensley opened this issue Dec 29, 2016 · 4 comments
Closed

Support benchmarking startup performance #335

cwensley opened this issue Dec 29, 2016 · 4 comments
Assignees
Milestone

Comments

@cwensley
Copy link

cwensley commented Dec 29, 2016

I am attempting to determine the startup performance of my library (Portable.Xaml), but it seems there's no option to only run the benchmark a single time.

I've tried using Job.Dry.With(RunStrategy.ColdStart) in my Config, but it still is running the benchmark twice.

Investigating the issue, it appears that this line in the generated benchmark calls the Engine.Jitting() method, which calls the benchmark, before running the benchmark.

Is there a way to get around this that I'm not seeing? If not, I think a config option to omit the Jitting() phase would be extremely useful.

Thanks for any help!

@adamsitnik
Copy link
Member

Hi @cwensley

I like your idea, I had the same problem few times.

@AndreyAkinshin maybe we should just ommit the jitting for ColdStart? What do you think? Or rather a new strategy? Once ?

@adamsitnik adamsitnik self-assigned this Dec 30, 2016
@adamsitnik adamsitnik added this to the v0.10.2 milestone Dec 30, 2016
@AndreyAkinshin
Copy link
Member

@cwensley, thanks for the report. The bug will be fixed in the next version of BenchmarkDotNet.
@adamsitnik, I will fix it. I almost finished a new RunStrategy (which solves one-time Setup/Cleanup) problem. So, I will also disable jitting for ColdStart and the new strategy. Hopefully, will be done on holidays.

@cwensley
Copy link
Author

Hey guys!

Thanks for the quick response, this will be really useful. I look forward to the next release to test it out!

Cheers,
Curtis.

@AndreyAkinshin
Copy link
Member

@cwensley, fixed, will be released soon. Also see IntroColdStart.

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

3 participants