spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Armbrust (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (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
Date Wed, 20 May 2015 19:27:04 GMT

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

Michael Armbrust updated SPARK-6759:
------------------------------------
    Target Version/s: 1.5.0  (was: 1.4.0)

> 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


Mime
View raw message