pitrou commented on PR #13661:
URL: https://github.com/apache/arrow/pull/13661#issuecomment-1191372761

   Ok, so I run locally with gcc 9.4.0 (Ubuntu 20.04) on AMD Zen 2.
   
   ### Build times
   
   * `-O3`:
   ```
   real 1m25,888s
   user 21m58,527s
   sys  0m48,888s
   ```
   
   * `-O2`:
   ```
   real 1m21,713s
   user 20m57,462s
   sys  0m48,843s
   ```
   
   * `-O2 -ftree-vectorize`:
   ```
   real 1m23,461s
   user 21m11,970s
   sys  0m49,485s
   ```
   
   ### Lib sizes
   
   * `-O3`:
   ```
      text         data     bss     dec     hex filename
   23230116      326105 2197509 25753730        188f882 
build-bundled-release/release/libarrow.so
   1276669        24928    2346 1303943  13e587 
build-bundled-release/release/libarrow_testing.so
   ```
   
   * `-O2`:
   ```
   22574451      326665 2197509 25098625        17ef981 
build-bundled-release/release/libarrow.so
   1268546        25144    2346 1296036  13c6a4 
build-bundled-release/release/libarrow_testing.so
   ```
   
   * `-O2 -ftree-vectorize`:
   ```
   22639315      326713 2197509 25163537        17ff711 
build-bundled-release/release/libarrow.so
   1257242        25144    2346 1284732  139a7c 
build-bundled-release/release/libarrow_testing.so
   ```
   
   ### Compute benchmarks
   
   * `-O2` vs `-O3`: 
https://gist.github.com/pitrou/e76b89f7e7e1f0e9a361410286c4a198
   * `-O2 -ftree-vectorize` vs `-O3`: 
https://gist.github.com/pitrou/feefd0819a513e6068dcd17b12d875e6
   * `-O2 -ftree-vectorize` vs `-O2`: 
https://gist.github.com/pitrou/083d0abd3f404be47716ae31cddda2db
   
   All in all, in this case:
   * the size and build time reductions are significant but small (less than 5%)
   * `-ftree-vectorize` brings a net performance improvement over bare `-O2`
   * performance seems globally comparable between `-O2 -ftree-vectorize` and 
`-O3`, despite some large disparities in individual micro-benchmarks
   


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