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

Posted to issues@spark.apache.org by "Michael Armbrust (JIRA)" <ji...@apache.org> on 2014/09/14 00:09:33 UTC

[jira] [Resolved] (SPARK-3294) Avoid boxing/unboxing when handling in-memory columnar storage

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

Michael Armbrust resolved SPARK-3294.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.0

> Avoid boxing/unboxing when handling in-memory columnar storage
> --------------------------------------------------------------
>
>                 Key: SPARK-3294
>                 URL: https://issues.apache.org/jira/browse/SPARK-3294
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 1.0.2, 1.1.0
>            Reporter: Cheng Lian
>            Assignee: Cheng Lian
>            Priority: Critical
>             Fix For: 1.2.0
>
>
> When Spark SQL in-memory columnar storage was implemented, we tried to avoid boxing/unboxing costs as much as possible, but {{javap}} shows that there still exist code that involves boxing/unboxing on critical paths due to type erasure, especially methods of sub-classes of {{ColumnType}}. Should eliminate them whenever possible for better performance.



--
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