Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14854
Another advantage of this PR's approach is straggler-resilience: imagine
that you're going to have to compute all partitions anyways and also assume
that some small number of partitions will
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14854
I thought of one significant UX improvement offered by the approach in this
withdrawn PR: when the current "multiple jobs" limit executes, there's no way
for the end user to know how much work
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14854
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/14854
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64866/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14854
**[Test build #64866 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64866/consoleFull)**
for PR 14854 at commit
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14854
I'm actually going to close this now and will revisit later; the scheduling
complexity may not be warranted now given benefits of simpler approaches.
---
If your project is set up for it, you
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14854
@davies brought up a reasonable point that we might be able to achieve
similar benefits with less complexity by replacing the exponential ramp-up with
something that's linearly proportional to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14854
**[Test build #64866 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64866/consoleFull)**
for PR 14854 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14854
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64826/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14854
Merged build finished. Test FAILed.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14854
**[Test build #64826 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64826/consoleFull)**
for PR 14854 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14854
**[Test build #64826 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64826/consoleFull)**
for PR 14854 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14854
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/14854
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64810/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14854
**[Test build #64810 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64810/consoleFull)**
for PR 14854 at commit
15 matches
Mail list logo
