-
Notifications
You must be signed in to change notification settings - Fork 28.5k
[SPARK-51947] Spark connect model cache offloading #50752
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
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
Signed-off-by: Weichen Xu <[email protected]>
.build[String, CacheItem]() | ||
.asMap() | ||
} else { | ||
new ConcurrentHashMap[String, CacheItem]() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think it is risky that mlcache has no memory limit when offloading is disabled? Probably it makes sense to keep the old behaviour in this case: mlcache also has memory limit and retention time when offloading is disabled, but once a model is evicted, future access to it will throw an error CACHE_INVALID. WDYT?
What changes were proposed in this pull request?
Support offloading model cache to spark driver local disk
Why are the changes needed?
Motivation: this feature helps to reduce spark driver memory pressure.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually.
Was this patch authored or co-authored using generative AI tooling?
No.