Maybe JIT? The 1st stage -- the scheduler code isn't JITed yet.
On Wed, May 13, 2015 at 9:18 AM, Akshat Aranya wrote:
> Hi,
> Any input on this? I'm willing to instrument further and experiment
> if there are any ideas.
>
> On Mon, May 4, 2015 at 11:27 AM, Akshat Aranya wrote:
> > Hi,
> >
> >
Hi,
Any input on this? I'm willing to instrument further and experiment
if there are any ideas.
On Mon, May 4, 2015 at 11:27 AM, Akshat Aranya wrote:
> Hi,
>
> I have been investigating scheduling delays in Spark and I found some
> unexplained anomalies. In my use case, I have two stages after
Hi,
I have been investigating scheduling delays in Spark and I found some
unexplained anomalies. In my use case, I have two stages after
collapsing the transformations: the first is a mapPartitions() and the
second is a sortByKey(). I found that the task serialization for the
first stage takes m
