You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Reynold Xin (JIRA)" <ji...@apache.org> on 2015/07/29 09:21:04 UTC

[jira] [Closed] (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

     [ https://issues.apache.org/jira/browse/SPARK-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reynold Xin closed SPARK-6759.
------------------------------
    Resolution: Won't Fix

Marking this as won't fix for now -- since maybe the solution is to replace the existing in-memory columnar format.


> 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
>            Priority: Critical
>
> 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