-
Notifications
You must be signed in to change notification settings - Fork 458
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
[VL] Disable background IO threads by default #7164
Comments
Hello @zhztheplayer , This feature would impact outr perf number, as remote stroage access takes time, this would help reduce it. Do we have any plan to fix the issues and re-enable it? |
Hi @zhli1142015 , as mentioned offline, issue #7161 is not a new one and should exist for long time. I assume your scenario is not memory-bound so IO threads could work stably without spilling. Although PR #7165 for this issue is filed, we can still be tracking on any possible solutions for #7161 after the PR is merged. And I am also adding one TPC benchmark job for |
Thanks, make sense. |
Velox's background IO threads (typically used for split preloading) have been causing some locking issues since it's not aligned with Spark's threading model. For example: #7161.
And it also causes slow runtime filter: facebookincubator/velox#10173.
So we are exploring opportunity to disable it by default until these related issues be resolved. Meanwhile would like to here from users for thoughts.
The text was updated successfully, but these errors were encountered: