Uh oh!
There was an error while loading. Please reload this page.
[SPARK-19486][CORE](try 3) Investigate using multiple threads for task serialization - #17139
[SPARK-19486][CORE](try 3) Investigate using multiple threads for task serialization#17139witgo wants to merge 2 commits into
Conversation
a06f8c8 to
6874d1eCompareSparkQA
commented
Mar 2, 2017
Test build #73775 has finished for PR 17139 at commit
|
SparkQA
commented
Mar 2, 2017
Test build #73776 has finished for PR 17139 at commit
|
SparkQA
commented
Mar 2, 2017
Test build #73769 has finished for PR 17139 at commit
|
SparkQA
commented
Mar 2, 2017
Test build #73771 has finished for PR 17139 at commit
|
6874d1e to
4d9b666CompareSparkQA
commented
Mar 3, 2017
Test build #73848 has finished for PR 17139 at commit
|
witgo
commented
Mar 8, 2017
kayousterhout
commented
Mar 8, 2017
Why is the time improvement so much larger here than in the other PR? |
witgo
commented
Mar 8, 2017
Added the multi-threaded code for serialization |
kayousterhout
commented
Mar 8, 2017
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? |
witgo
commented
Mar 9, 2017
@kayousterhout The test report has been updated. |
4d9b666 to
8fbe15cCompareSparkQA
commented
Mar 9, 2017
Test build #74270 has finished for PR 17139 at commit
|
jiangxb1987
commented
Jun 21, 2017
@witgo Are you still working on this? |
witgo
commented
Jun 22, 2017
@jiangxb1987 ,Yes do you have any questions? |
jiangxb1987
commented
Jun 22, 2017
Please bring this PR up to date, then maybe some guy can review this. :) |
srowen
commented
Jun 22, 2017
This should probably just be closed |
gatorsmile
commented
Jun 27, 2017
We are closing it due to inactivity. please do reopen if you want to push it forward. Thanks! |
## What changes were proposed in this pull request? This PR proposes to close stale PRs, mostly the same instances with apache#18017 I believe the author in apache#14807 removed his account. Closesapache#7075Closesapache#8927Closesapache#9202Closesapache#9366Closesapache#10861Closesapache#11420Closesapache#12356Closesapache#13028Closesapache#13506Closesapache#14191Closesapache#14198Closesapache#14330Closesapache#14807Closesapache#15839Closesapache#16225Closesapache#16685Closesapache#16692Closesapache#16995Closesapache#17181Closesapache#17211Closesapache#17235Closesapache#17237Closesapache#17248Closesapache#17341Closesapache#17708Closesapache#17716Closesapache#17721Closesapache#17937 Added: Closesapache#14739Closesapache#17139Closesapache#17445Closesapache#18042Closesapache#18359 Added: Closesapache#16450Closesapache#16525Closesapache#17738 Added: Closesapache#16458Closesapache#16508Closesapache#17714 Added: Closesapache#17830Closesapache#14742 ## How was this patch tested? N/A Author: hyukjinkwon <gurwls223@gmail.com> Closesapache#18417 from HyukjinKwon/close-stale-pr.
What changes were proposed in this pull request?
See https://issues.apache.org/jira/browse/SPARK-19486
In the case of stage has a lot of tasks, this PR can improve the scheduling performance of
15%The test code:
and
spark-defaults.conffile:The test results are as follows
How was this patch tested?
Existing tests.