I'm seeing many threads doing deserialization of a task, I understand since lambda is involved, we can't use Kryo for those purposes. However I'm running it in local mode, this serialization is not really necessary, no?
Is there any trick I can apply to get rid of this thread contention ? I'm seeing many of the below threads in thread dumps ... "Executor task launch worker for task 11.0 in stage 15472514.0 (TID 19788863)" #732821 daemon prio=5 os_prio=0 tid=0x00007f02581b2800 nid=0x355d waiting for monitor entry [0x00007effd1e3f000] java.lang.Thread.State: BLOCKED (on object monitor) at java.lang.ClassLoader.loadClass(ClassLoader.java:400) - waiting to lock <0x00007f0f7246edf8> (a java.lang.Object) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355) at java.lang.ClassLoader.loadClass(ClassLoader.java:351) at scala.runtime.LambdaDeserializer$.deserializeLambda(LambdaDeserializer.scala:51) at scala.runtime.LambdaDeserialize.deserializeLambda(LambdaDeserialize.java:38) Thanks -Kohki
