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

Repair and disable failing benchmarks #16173

Merged
merged 1 commit into from
Jun 20, 2019
Merged

Repair and disable failing benchmarks #16173

merged 1 commit into from
Jun 20, 2019

Conversation

roji
Copy link
Member

@roji roji commented Jun 20, 2019

Our current query pipeline makes some benchmarks fail. Unfortunately the ASP.NET perf lab currently ignores the entire benchmark suite if any benchmark fails, so disabled those benchmarks for now. This should allow us to start tracking some basic query scenarios.

Also modified benchmarks to access int rather decimal (the latter is limited on Sqlite).

We may want to add some more benchmarks - will look into this at some point (but if someone has ideas...).

FYI to manually run benchmarks on the console, just go into benchmark/EFCore.Sqlite.Benchmarks and do dotnet run -c Release -f netcoreapp3.0 -- --inProcess. You can add --filter to invoke a specific suite or method.

Copy link
Member

@smitpatel smitpatel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix SelectComposed.

Our current query pipeline makes some benchmarks fail. Unfortunately the
ASP.NET perf lab currently ignores the entire benchmark suite if any
benchmark fails, so disabled those benchmarks for now.

Also modified benchmarks to access int rather decimal (the latter is
limited on Sqlite).
@roji roji merged commit 1c14b58 into master Jun 20, 2019
@ghost ghost deleted the MoarBenchmarks branch June 20, 2019 23:52
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

Successfully merging this pull request may close these issues.

2 participants