[
https://issues.apache.org/jira/browse/SPARK-26337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717281#comment-16717281
]
ASF GitHub Bot commented on SPARK-26337:
----------------------------------------
SparkQA removed a comment on issue #23284: [SPARK-26337][SQL][TEST] Add
benchmark for LongToUnsafeRowMap
URL: https://github.com/apache/spark/pull/23284#issuecomment-446197580
**[Test build #99974 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/99974/testReport)**
for PR 23284 at commit
[`cdbae0a`](https://github.com/apache/spark/commit/cdbae0a43d4ae01889feb66f5e0e7d55799e6dda).
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
> Priority: Major
>
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
