Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/15505
It looks like you've added multi-threading for task serialization here,
which I'm hesitant about for reasons @squito discussed in the JIRA (namely, I
think reducing the size of the data serialized for each task, as in
SPARK-19108, is a better first step to reducing the serialization bottleneck).
Can you limit this PR to just handle SPARK-18890, so it just moves
serialization from the TaskSetManager to the CoarseGrainedSchedulerBackend (as
had been done in the previous version of this PR)? Then let's discuss /
address SPARK-1141 separately (which is the old JIRA to parallelize task
serialization -- I stumbled on this yesterday, and we should use that to
continue the discussion).
---
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 wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
