spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Spark (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (SPARK-23879) Introduce MemoryBlock API instead of Platform API with Object
Date Fri, 06 Apr 2018 04:46:00 GMT

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

Apache Spark reassigned SPARK-23879:
------------------------------------

    Assignee: Apache Spark

> Introduce MemoryBlock API instead of Platform API with Object 
> --------------------------------------------------------------
>
>                 Key: SPARK-23879
>                 URL: https://issues.apache.org/jira/browse/SPARK-23879
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core, SQL
>    Affects Versions: 2.3.0
>            Reporter: Kazuaki Ishizaki
>            Assignee: Apache Spark
>            Priority: Major
>
> This JIRA is derived from SPARK-10399.
> During the discussion, the community revealed that current Spark framework directly accesses
several types of memory regions (e.g. {{byte[]}}, {{long[]}}, or {{Off-heap}}) by using {{Platform
API with }}{{Object}} type. It would be good to have unified memory management API for clear
memory model.
> It is also good for performance. If we can pass typed object (e.g.{{byte[]}}, {{long[]}})
to {{Platform.getXX()/putXX()}}, it is faster than using {{Platform.getXX(Object)/putXX(Object,
...)}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message