Skip to content

Conversation

LuciferYang
Copy link
Contributor

@LuciferYang LuciferYang commented Apr 15, 2025

What changes were proposed in this pull request?

This pr aims to upgrade kryo-shaded from 4.0.2 to 4.0.3.

Why are the changes needed?

This version brings some bug fixes and performance improvements related to chunked encoding:

full changes as follows:

Does this PR introduce any user-facing change?

No

How was this patch tested?

  • Pass GitHub Actions

Was this patch authored or co-authored using generative AI tooling?

No

@LuciferYang LuciferYang marked this pull request as draft April 15, 2025 03:34
<artifactId>kryo-shaded</artifactId>
<version>${kryo.version}</version>
</dependency>
<dependency>
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Kryo 4.0.x depends on version objenesis 2.5.1 , while Spark currently depends on objenesis 3.3. Here, it is uniformly defined as version 3.3.

Copy link
Member

Choose a reason for hiding this comment

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

Shall we use exclusion ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think it's necessary to use exclusion. But just to be on the safe side, let me exclude it

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

@LuciferYang
Copy link
Contributor Author

cc @yaooqinn Let's test 4.0.3 first

@LuciferYang LuciferYang changed the title Test kryo 4.0.3 [SPARK-51806][BUILD] Upgrade kryo-shaded to 4.0.3 Apr 15, 2025
@LuciferYang
Copy link
Contributor Author

will update bench result later

basicTypes: Double with unsafe:false 222 225 2 4.5 221.9 0.7X
Array: Int with unsafe:false 13 14 1 78.0 12.8 12.9X
Array: Long with unsafe:false 21 21 1 48.2 20.8 8.0X
Array: Float with unsafe:false 6 6 0 178.9 5.6 29.6X
Copy link
Contributor

Choose a reason for hiding this comment

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

Double in throughput 🤔
Are we are expecting this kind of improvement on a hotfix bump I wonder.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

image

image

@hiufung-kwok Judging from the historical update records, the current data seems relatively normal, whereas the previous update results may have had some unknown errors. It is also possible that there are certain unstable factors affecting the results of this test case, which could be worth investigating.

@LuciferYang LuciferYang marked this pull request as ready for review April 16, 2025 02:47
@LuciferYang
Copy link
Contributor Author

LuciferYang commented Apr 16, 2025

friendly ping @yaooqinn

@yaooqinn yaooqinn closed this in fd44ab6 Apr 16, 2025
@yaooqinn
Copy link
Member

Merged to master. Can you backport @LuciferYang since it's a bugfix release of Kryo?

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

Successfully merging this pull request may close these issues.

3 participants