steven-aerts opened a new pull request, #1708:
URL: https://github.com/apache/avro/pull/1708

   Update the compiler to generate the implementation of the `.equals()` and 
`.hashCode() function, instead of relying on the
   implementation of GenericData.  This improves the performance of those 
functions significantly.
   
   The generated implementations are factor 10 to 20 faster for `.equals()` and 
a factor 5 to 10 for `.hashCode()`.
   
   The implementation generates the same hashCode as the genericData, which is 
validated by existing tests
   
   Result of Perf test before the change:
   
   ```
   Benchmark              Mode  Cnt          Score             Error  Units
   SpecficTest.equals    thrpt    3   12598610.194 +/-  11160265.279  ops/s
   SpecficTest.hashCode  thrpt    3   24729446.862 +/-  29051332.794  ops/s
   ```
   
   Results using generated functions:
   
   ```
   Benchmark              Mode  Cnt          Score             Error  Units
   SpecficTest.equals    thrpt    3  211314296.950 +/- 104154793.126  ops/s
   SpecficTest.hashCode  thrpt    3  180349506.632 +/- 143639246.771  ops/s
   ```
   
   ### Jira
   
   - [x] My PR addresses the following: 
[AVRO-3527](https://issues.apache.org/jira/browse/AVRO-3527) Generated equals() 
and hashCode() for SpecificRecords
   
   ### Tests
   
   - [x] My PR adds the following unit tests:
   * TestUtf8#testHashCodeSameAsString()
   * TestGeneratedCode#ignoredFields()
   * JMH test for SpecificRecords `equals()` and `hashCode()`
   
   ### Commits
   
   - [x] My commits all reference Jira issues in their subject lines. In 
addition, my commits follow the guidelines from "[How to write a good git 
commit message](https://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [x] In case of new functionality, my PR adds documentation that describes 
how to use it.
     - All the public functions and the classes in the PR contain Javadoc that 
explain what it does
   


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

Reply via email to