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

[SPARK-25895][Core]Adding testcase to compare Lz4 and Zstd compression #22906

Closed
wants to merge 1 commit into from

Conversation

Udbhav30
Copy link
Contributor

What changes were proposed in this pull request?

Added a UT to verify Zstd compression algorithm has better compression ratio than lz4 in shuffle read/write and spill

How was this patch tested?

Added UT

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@srowen
Copy link
Member

srowen commented Oct 31, 2018

I don't think this tests something about the correctness of Spark though. I am not sure this is worth it.

@@ -128,6 +130,69 @@ class CompressionCodecSuite extends SparkFunSuite {
}
}

test("SPARK-25895 Zstd shuffle Read/Write/spill comparison w.r.t lz4") {
Copy link
Member

Choose a reason for hiding this comment

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

How about add a benchmark? You can check our all benchmarks here:: https://issues.apache.org/jira/browse/SPARK-25475

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for your suggestion, i will go through the benchmarks and update the PR

@srowen
Copy link
Member

srowen commented Nov 2, 2018

Benchmarks aren't run with tests right? That's fine. I am still not sure Spark is the best place for this.

@srowen
Copy link
Member

srowen commented Nov 10, 2018

Ping @Udbhav30

@Udbhav30
Copy link
Contributor Author

Okay I'll close this PR

@Udbhav30 Udbhav30 closed this Nov 10, 2018
@Udbhav30 Udbhav30 deleted the perfTest branch January 23, 2020 06:56
@hackeryang
Copy link

It was tested in Trino, please see: trinodb/trino#20274

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants