You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (JIRA)" <ji...@apache.org> on 2018/12/14 03:19:00 UTC

[jira] [Resolved] (SPARK-26337) Add benchmark for LongToUnsafeRowMap

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

Wenchen Fan resolved SPARK-26337.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0

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

> Add benchmark for LongToUnsafeRowMap
> ------------------------------------
>
>                 Key: SPARK-26337
>                 URL: https://issues.apache.org/jira/browse/SPARK-26337
>             Project: Spark
>          Issue Type: Test
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: Liang-Chi Hsieh
>            Assignee: Liang-Chi Hsieh
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Regarding the performance issue of SPARK-26155, I think it is better to add a benchmark for LongToUnsafeRowMap which is the root cause of performance regression. It can be easier to show performance difference between different metric implementation in LongToUnsafeRowMap.



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