You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Yin Huai (JIRA)" <ji...@apache.org> on 2015/04/08 04:35:12 UTC
[jira] [Created] (SPARK-6759) Do not borrow/release a kryo instance
for every value in a complex type value when doing
serialization/deserialization in in-memory columnar store
Yin Huai created SPARK-6759:
-------------------------------
Summary: Do not borrow/release a kryo instance for every value in a complex type value when doing serialization/deserialization in in-memory columnar store
Key: SPARK-6759
URL: https://issues.apache.org/jira/browse/SPARK-6759
Project: Spark
Issue Type: Improvement
Components: SQL
Reporter: Yin Huai
Right now, for columns of map, array, and struct types, we borrow/release a kryo instance when serializing/deserializing every value, which is really expensive (the kryo pool is backed by a ArrayBlockingQueue). It will be good if we borrow before the serialization/deserialization and release it after we have done all of the work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org