[SPARK-58854][ML] Optimize GeneralizedLinearRegressionModel transform closure - #58100
Open
zhengruifeng wants to merge 1 commit into
Open
[SPARK-58854][ML] Optimize GeneralizedLinearRegressionModel transform closure#58100zhengruifeng wants to merge 1 commit into
zhengruifeng wants to merge 1 commit into
Conversation
HyukjinKwon
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR optimizes
GeneralizedLinearRegressionModel.transformby snapshotting the predictionstate before creating transform UDFs. The UDFs now capture only the required coefficients,
intercept, and
FamilyAndLinkinstead of the full model.The public prediction methods continue to use the same prediction logic through companion helper
methods.
Why are the changes needed?
Avoiding the model capture reduces transform-closure retained memory, which is useful for Spark
Connect server workloads and follows the closure-size optimizations tracked under SPARK-58584.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Ran local static checks:
Measured serialized
ScalaUDF.functionclosure size with a temporary local probe:directPredictionlinkAndPredictiontotalFor
linkAndPrediction, the two UDF closures measured individually as:udf#0udf#1No unit test was added because this is an internal refactor of existing prediction logic.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Codex (GPT-5)