Skip to content

Benchmark: replace shell scripts with JS code #1470

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Aug 25, 2018
Merged

Conversation

IvanGoncharov
Copy link
Member

In order to have a better discussion around #1463 we need to add benchmarks for validate and validateSDL. I split out refactoring part into this PR.
@mjmahone Can you please take a look?

@mjmahone
Copy link
Contributor

I don't think I have enough context around what we're doing with the benchmarks to give this a proper review. @leebyron might be needed here.

Copy link
Contributor

@mjmahone mjmahone left a comment

Choose a reason for hiding this comment

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

Just to make sure my review is accurate, I'd like to make sure I understand how the benchmark runner works.

We provide two revisions to compare against. Then we run all the benchmark tests to run, and run them one at a time using runBenchmark.

Given that understanding, this looks good.

@IvanGoncharov
Copy link
Member Author

IvanGoncharov commented Aug 25, 2018

We provide two revisions to compare against. Then we run all the benchmark tests to run, and run them one at a time using runBenchmark.

@mjmahone Yes, exactly.
More context and description in my original PR: #1167

We provide two revisions

It's not limited to two you can provide any number 😉

@IvanGoncharov IvanGoncharov merged commit 4643705 into master Aug 25, 2018
@IvanGoncharov IvanGoncharov deleted the cleanupBenchmark branch August 25, 2018 21:45
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants