getFiberSerializer currently constructs the kryo instance every time parkAndSerialize is called, and unfortunately there's no way to get around this, even if that serializer is not required. As the call is quite slow this shows up as a hotspot during profiling. It should either be pooled or some functionality should be exposed to control whether to create it or not.
getFiberSerializercurrently constructs the kryo instance every timeparkAndSerializeis called, and unfortunately there's no way to get around this, even if that serializer is not required. As the call is quite slow this shows up as a hotspot during profiling. It should either be pooled or some functionality should be exposed to control whether to create it or not.