phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "bd2019us (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-5224) Iteratively executing the same SQL query will greatly damage the performance
Date Mon, 01 Apr 2019 22:18:00 GMT
bd2019us created PHOENIX-5224:
---------------------------------

             Summary: Iteratively executing the same SQL query will greatly damage the performance
                 Key: PHOENIX-5224
                 URL: https://issues.apache.org/jira/browse/PHOENIX-5224
             Project: Phoenix
          Issue Type: Bug
            Reporter: bd2019us


Locations: 

(1) phoenix-core/src/it/java/org/apache/phoenix/end2end/index/IndexRebuildIncrementDisableCountIT.java:170

(2) phoenix-queryserver/src/it/java/org/apache/phoenix/end2end/HttpParamImpersonationQueryServerIT.java:383

(3) phoenix-core/src/it/java/org/apache/phoenix/tx/TxCheckpointIT.java:108

(4) phoenix-core/src/it/java/org/apache/phoenix/end2end/DeleteIT.java:794,858

(5) phoenix-core/src/it/java/org/apache/phoenix/end2end/UpsertSelectAutoCommitIT.java:240

(6) phoenix-core/src/it/java/org/apache/phoenix/end2end/DropTableIT.java:35

(7) phoenix-queryserver/src/it/java/org/apache/phoenix/end2end/SecureQueryServerIT.java:297

At these locations, the java.sql.Statement is intensively used in a loop and executing the
same SQL query, which will highly damage the performance of database access. In such cases,
java.sql.PreparedStatement should be used to enable the database compiling the SQL command
ahead of time, which has a much better performance compared with Statement.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message