-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-5269] [CORE] Use a SerializerInstance pool in BlockManager. #8292
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
Conversation
|
Jenkins, test this please |
|
ok to test |
|
@maciej-kisiel have you done any benchmarking on this? |
|
Test build #41892 has finished for PR 8292 at commit
|
a3bddec to
492c06a
Compare
|
@andrewor14 I'm working on it |
|
Test build #42138 has finished for PR 8292 at commit
|
|
Weird, I just rebased it.. |
|
Yeah master tests are flaky. retest this please |
|
Test build #42276 has finished for PR 8292 at commit
|
|
@maciej-kisiel could you rebase this one? |
|
@maciej-kisiel any updates on this one? Do you still plan to work on this? |
|
It will be difficult for me to benchmark this, because in the meantime I lost access to a big data environment. |
|
I can see how this patch can improve performance; currently we may end up creating a |
|
Agree, do you mind closing this PR? |
Instead of creating a serializer instance each time the BlockManager serialization methods are used, keep a pool of available serializers. It should improve performance.