xinghuayu007 opened a new pull request #6324:
URL: https://github.com/apache/incubator-doris/pull/6324


   ## Proposed changes
   
   Currently, `ltrim` and `rtrim` function can only compare one character with 
blank at a time. For 128 bits register, it can compare 16 characters at a time 
using SIMD. Therefore, using SIMD can speedup performance greatly.  When there 
is less than 2 blanks, vetorized-ltrim has the same performance with 
non-vectorized-ltrim, but when blanks are more than 3, performance can be 
improved more than 2-3 times. Here are the test results:
   
   **tests 1000 times, the unit is ns**
   
   **ltrim function:**
   2 blanks
   vectorization: 60944
   normal: 68471
   
   3 blanks
   vectorization: 70170
   normal: 83194
   
   8 blanks
   vectorization: 75192
   normal: 152855
   
   22 blanks
   wangxixu-vectorization: 77532
   wangxixu-normal: 255719
   
   
   **rtrim functions:**
   2 blanks
   vectorization: 88203
   normal: 122999
   
   3 blanks
   vectorization: 79561
   normal: 130995
   
   8 blanks
   vectorization: 15061465
   normal: 2498301
   
   22
   vectorization: 96263
   normal: 316270
   
   _**The code refers no any other system, implemented by myself.**_
   
   ## Types of changes
   
   What types of changes does your code introduce to Doris?
   _Put an `x` in the boxes that apply_
   
   - [ ] Bugfix (non-breaking change which fixes an issue)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to not work as expected)
   - [ ] Documentation Update (if none of the other choices apply)
   - [ ] Code refactor (Modify the code structure, format the code, etc...)
   - [ ] Optimization. Including functional usability improvements and 
performance improvements.
   - [ ] Dependency. Such as changes related to third-party components.
   - [ ] Other.
   
   ## Checklist
   
   _Put an `x` in the boxes that apply. You can also fill these out after 
creating the PR. If you're unsure about any of them, don't hesitate to ask. 
We're here to help! This is simply a reminder of what we are going to look for 
before merging your code._
   
   - [ ] I have created an issue on (Fix #ISSUE) and described the bug/feature 
there in detail
   - [ ] Compiling and unit tests pass locally with my changes
   - [ ] I have added tests that prove my fix is effective or that my feature 
works
   - [ ] If these changes need document changes, I have updated the document
   - [ ] Any dependent changes have been merged
   
   ## Further comments
   
   If this is a relatively large or complex change, kick off the discussion at 
[email protected] by explaining why you chose the solution you did and what 
alternatives you considered, etc...
   


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