yew1eb opened a new issue, #1926:
URL: https://github.com/apache/auron/issues/1926

   Taking the tpcds query slice **[Test spark-3.5 JDK21 Scala-2.13 / Run TPC-DS 
test q70,q71,q72,q73,q74,q75,q76,q77,q78,q79]** as an example, Auron queries 
are **significantly slower than Spark** in the CI test
   
   
   <img width="549" height="370" alt="Image" 
src="https://github.com/user-attachments/assets/e4f251bf-999b-4d78-a9cf-118fff62a197";
 />
   
   ## Root Cause Identified
   The performance regression is caused by a **CI configuration change**: the 
Rust compilation optimization level was adjusted from `opt-level = 1` to 
`opt-level = 0`.
   
   ## Verification with Opt-Level Adjustment
   When reverting the Rust compilation config to `opt-level = 1`, **Auron 
outperforms Spark** in the same TPC-DS test slice:
   
   
   <img width="497" height="339" alt="Image" 
src="https://github.com/user-attachments/assets/bc56e3fa-ce28-4a36-b65d-06cd2ae6e537";
 />
   
   ## Compilation vs Performance Tradeoff
   1. **`opt-level = 0` (Current CI Config)**
      - Minimal reduction in Rust compilation time (negligible gain)
      - Severe TPC-DS query performance degradation, with total runtime 
extended to **56 minutes**
   
   <img width="573" height="623" alt="Image" 
src="https://github.com/user-attachments/assets/fdd8bae9-ec48-4257-9263-b38a3f602dd6";
 />
   
   2. **`opt-level = 1` (Recommended Config)**
      - Slight increase in Rust compilation time (acceptable overhead)
      - Dramatic TPC-DS query performance improvement, with total runtime 
**greatly reduced**
   
   <img width="486" height="590" alt="Image" 
src="https://github.com/user-attachments/assets/acd8a6e6-6f50-4332-86e9-45b28ac01673";
 />
   
   ## Suggestion
   Revert the Rust compilation optimization level in CI from `opt-level = 0` to 
`opt-level = 1` to ensure Auron's TPC-DS query performance is optimized.
   


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