[GitHub] [incubator-paimon] fujianhua168 opened a new issue, #2067: [Feature] Presto/Trino has poor read performance and needs to be enhanced

["fujianhua168 (via GitHub)" <gi...@apache.org>]

fujianhua168 opened a new issue, #2067:
URL: https://github.com/apache/incubator-paimon/issues/2067

   ### Search before asking
   
   - [X] I searched in the [issues](https://github.com/apache/incubator-paimon/issues) and found nothing similar.
   
   
   ### Motivation
   
      After the launch of the Presto333 support for reading Paimon tables, many users in our company reported that querying Paimon tables through Presto333 was too slow. After repeated testing and check  in multiple SQL scenarios, it was found that this issue does exist (note: compared to querying Hive tables, Presto queries Paimon tables take 3-6 times longer, but Spark reading performance is much better). The following is a screenshot of the check result: 
   ![image](https://github.com/apache/incubator-paimon/assets/5379274/a2361f03-36c1-44a2-9823-8e0fbdef1860)
   
   We hope to enhance the performance of Presto333 in querying Paimon tables (similar to Spark3): querying Paimon tables takes almost as much time as directly querying Hive tables
   
   ### Solution
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] I'm willing to submit a PR!


-- 
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: issues-unsubscribe@paimon.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Feature] Presto/Trino has poor read performance and needs to be enhanced [paimon]

["DataGamePlay (via GitHub)" <gi...@apache.org>]

DataGamePlay commented on issue #2067:
URL: https://github.com/apache/paimon/issues/2067#issuecomment-3722142630

   ## Reproduce on 0.8.1
   Same issue on **Paimon 0.8.1** 
   ## Problem Description
   Same data, same Hive engine, same query logic:
   - Hive table: 2 minutes
   - Paimon table: 6 minutes (still not returned)
   
   Same data, same Spark SQL:
   - Direct SELECT fields: very slow
   - GROUP BY fields: very fast
   
   3. Query with Hive engine:
   SELECT col1, col2 FROM paimon_table WHERE dt>='2025-01-01';
   -- 6 minutes, still not returned
   
   4. Query with Spark SQL:
   SELECT col1, col2 FROM paimon_table WHERE dt='2025-01-01';
   -- very slow
   
   SELECT col1, col2 FROM paimon_table WHERE dt='2025-01-01' GROUP BY col1, col2;
   -- very fast
   
   **Request**:  
   1.Please help analyze why direct SELECT is very slow even after read optimization, and why GROUP BY is very fast.


-- 
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: issues-unsubscribe@paimon.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org