yaooqinn opened a new pull request, #46972:
URL: https://github.com/apache/spark/pull/46972

   ### What changes were proposed in this pull request?
   <!--
   Please clarify what changes you are proposing. The purpose of this section 
is to outline the changes and how this PR fixes the issue. 
   If possible, please consider writing useful notes for better and faster 
reviews in your PR. See the examples below.
     1. If you refactor some codes with changing classes, showing the class 
hierarchy will help reviewers.
     2. If you fix some SQL features, you can provide some references of other 
DBMSes.
     3. If there is design documentation, please add the link.
     4. If there is a discussion in the mailing list, please add the link.
   -->
   
   Currently, we use two heximal string parsing functions. One uses Apache 
Codecs Hex for X-prefixed lit parsing, and the other use builtin impl for unhex 
function. I did a benchmark for them comparing with the `java.util.HexFormat` 
which was introduced in JDK17.
   
   ```
   OpenJDK 64-Bit Server VM 17.0.10+0 on Mac OS X 14.5
   Apple M2 Max
   Cardinality 1000000:                      Best Time(ms)   Avg Time(ms)   
Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
   
------------------------------------------------------------------------------------------------------------------------
   Apache                                             5050           5100       
   86          0.2        5050.1       1.0X
   Spark                                              3822           3840       
   30          0.3        3821.6       1.3X
   Java                                               2462           2522       
   87          0.4        2462.1       2.1X
   
   OpenJDK 64-Bit Server VM 17.0.10+0 on Mac OS X 14.5
   Apple M2 Max
   Cardinality 2000000:                      Best Time(ms)   Avg Time(ms)   
Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
   
------------------------------------------------------------------------------------------------------------------------
   Apache                                            10020          10828       
 1154          0.2        5010.1       1.0X
   Spark                                              6875           6966       
  144          0.3        3437.7       1.5X
   Java                                               4999           5092       
   89          0.4        2499.3       2.0X
   
   OpenJDK 64-Bit Server VM 17.0.10+0 on Mac OS X 14.5
   Apple M2 Max
   Cardinality 4000000:                      Best Time(ms)   Avg Time(ms)   
Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
   
------------------------------------------------------------------------------------------------------------------------
   Apache                                            20090          20433       
  433          0.2        5022.5       1.0X
   Spark                                             13389          13620       
  229          0.3        3347.2       1.5X
   Java                                              10023          10069       
   42          0.4        2505.6       2.0X
   
   OpenJDK 64-Bit Server VM 17.0.10+0 on Mac OS X 14.5
   Apple M2 Max
   Cardinality 8000000:                      Best Time(ms)   Avg Time(ms)   
Stdev(ms)    Rate(M/s)   Per Row(ns)   Relative
   
------------------------------------------------------------------------------------------------------------------------
   Apache                                            40277          43453       
 2755          0.2        5034.7       1.0X
   Spark                                             27145          27380       
  311          0.3        3393.1       1.5X
   Java                                              19980          21198       
 1473          0.4        2497.5       2.0X
   ```
   
   The results indicate that the speed is Apache Codecs < builtin < Java, 
increasing by ~50%.
   
   In this PR, we replace these two with the Java 17 API
   
   ### Why are the changes needed?
   <!--
   Please clarify why the changes are needed. For instance,
     1. If you propose a new API, clarify the use case for a new API.
     2. If you fix a bug, you can clarify why it is a bug.
   -->
   
   performance enhance
   
   
   ### Does this PR introduce _any_ user-facing change?
   <!--
   Note that it means *any* user-facing change including all aspects such as 
the documentation fix.
   If yes, please clarify the previous behavior and the change this PR proposes 
- provide the console output, description and/or an example to show the 
behavior difference if possible.
   If possible, please also clarify if this is a user-facing change compared to 
the released Spark versions or within the unreleased branches such as master.
   If no, write 'No'.
   -->
   no
   
   ### How was this patch tested?
   <!--
   If tests were added, say they were added here. Please make sure to add some 
test cases that check the changes thoroughly including negative and positive 
cases if possible.
   If it was tested in a way different from regular unit tests, please clarify 
how you tested step by step, ideally copy and paste-able, so that other 
reviewers can test and check, and descendants can verify in the future.
   If tests were not added, please describe why they were not added and/or why 
it was difficult to add.
   If benchmark tests were added, please run the benchmarks in GitHub Actions 
for the consistent environment, and the instructions could accord to: 
https://spark.apache.org/developer-tools.html#github-workflow-benchmarks.
   -->
   
   benchmarking 
   
   existing unit tests in 
org.apache.spark.sql.catalyst.expressions.MathExpressionsSuite
   
   ### Was this patch authored or co-authored using generative AI tooling?
   <!--
   If generative AI tooling has been used in the process of authoring this 
patch, please include the
   phrase: 'Generated-by: ' followed by the name of the tool and its version.
   If no, write 'No'.
   Please refer to the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
   -->
   no


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to