Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17139
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17139
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74270/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17139
**[Test build #74270 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74270/testReport)**
for PR 17139 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17139
**[Test build #74270 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74270/testReport)**
for PR 17139 at commit
Github user witgo commented on the issue:
https://github.com/apache/spark/pull/17139
@kayousterhout The test report has been updated.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/17139
Can you also post the time differences for some smaller jobs (e.g., 100
tasks, 1000 tasks, 10K tasks) to get a sense of how this varies with size?
---
If your project is set up for it, you
Github user witgo commented on the issue:
https://github.com/apache/spark/pull/17139
Added the multi-threaded code for serialization `TaskDescription` .
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/17139
Why is the time improvement so much larger here than in the other PR?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user witgo commented on the issue:
https://github.com/apache/spark/pull/17139
ping @kayousterhout @squito
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
