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

BenchmarkRunner should produce JSON summary file even when queries fail #1029

Merged

Conversation

andygrove
Copy link
Contributor

@andygrove andygrove commented Oct 27, 2020

This PR updates the benchmark runner to capture query plans even when query execution fails.

This closes #1027

@andygrove andygrove changed the title [WIP] Benchmark capture failed queries BenchmarkRunner should produce JSON summary file even when queries fail Oct 27, 2020
@sameerz sameerz added the benchmark Benchmarking, benchmarking tools label Oct 28, 2020
println(s"*** Iteration $i failed after $elapsed msec.")
queryTimes.append(-1)
exceptions.append(e.toString)
e.printStackTrace()
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think e.toString may omit the stack trace itself, even though it's printed. Do you think it makes sense to include them in the report? In that case we can print to a stream or writer using: https://docs.oracle.com/javase/7/docs/api/java/lang/Throwable.html#printStackTrace(java.io.PrintStream).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

So far I was able to get away with this approach because the exceptions are generally coming from the executors and the stack trace is already part of the message, but you're right, it would be better to do the full stack trace. I'll make that change today.

@andygrove andygrove self-assigned this Nov 2, 2020
abellina
abellina previously approved these changes Nov 2, 2020
@abellina
Copy link
Collaborator

abellina commented Nov 2, 2020

build

@abellina
Copy link
Collaborator

abellina commented Nov 3, 2020

@andygrove there's some mvn verify type errors in the build for import order, FYI.

Signed-off-by: Andy Grove <andygrove@nvidia.com>
Signed-off-by: Andy Grove <andygrove@nvidia.com>
Signed-off-by: Andy Grove <andygrove@nvidia.com>
Signed-off-by: Andy Grove <andygrove@nvidia.com>
@andygrove
Copy link
Contributor Author

build

2 similar comments
@andygrove
Copy link
Contributor Author

build

@pxLi
Copy link
Collaborator

pxLi commented Nov 4, 2020

build

@andygrove
Copy link
Contributor Author

@abellina The build is passing now. Could you re-approve?

@abellina abellina merged commit abb6e32 into NVIDIA:branch-0.3 Nov 4, 2020
sperlingxx pushed a commit to sperlingxx/spark-rapids that referenced this pull request Nov 20, 2020
…il (NVIDIA#1029)

* capture query plan and exceptions for failed queries

Signed-off-by: Andy Grove <andygrove@nvidia.com>
@andygrove andygrove deleted the benchmark-capture-failed-queries branch December 17, 2020 15:27
nartal1 pushed a commit to nartal1/spark-rapids that referenced this pull request Jun 9, 2021
…il (NVIDIA#1029)

* capture query plan and exceptions for failed queries

Signed-off-by: Andy Grove <andygrove@nvidia.com>
nartal1 pushed a commit to nartal1/spark-rapids that referenced this pull request Jun 9, 2021
…il (NVIDIA#1029)

* capture query plan and exceptions for failed queries

Signed-off-by: Andy Grove <andygrove@nvidia.com>
tgravescs pushed a commit to tgravescs/spark-rapids that referenced this pull request Nov 30, 2023
…IDIA#1029)

Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
benchmark Benchmarking, benchmarking tools
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEA] BenchmarkRunner should produce JSON summary file even when queries fail
4 participants