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

Posted to issues@spark.apache.org by "DB Tsai (JIRA)" <ji...@apache.org> on 2018/08/15 00:04:00 UTC

[jira] [Resolved] (SPARK-25115) Eliminate extra memory copy done when a ByteBuf is used that is backed by > 1 ByteBuffer.

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

DB Tsai resolved SPARK-25115.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 2.4.0

Issue resolved by pull request 22105
[https://github.com/apache/spark/pull/22105]

>     Eliminate extra memory copy done when a ByteBuf is used that is backed by > 1 ByteBuffer.
> ---------------------------------------------------------------------------------------------
>
>                 Key: SPARK-25115
>                 URL: https://issues.apache.org/jira/browse/SPARK-25115
>             Project: Spark
>          Issue Type: Improvement
>          Components: Input/Output
>    Affects Versions: 2.3.1
>            Reporter: Norman Maurer
>            Assignee: Norman Maurer
>            Priority: Major
>             Fix For: 2.4.0
>
>
> Calling ByteBuf.nioBuffer(...) can be costly when the ByteBuf is backed by more then 1 ByteBuf. In this case it makes more sense to call ByteBuf.nioBuffers(...) and iterate over the returned ByteBuffer[].



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