From dev-return-55933-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Tue Apr 2 00:47:02 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 167E6180621 for ; Tue, 2 Apr 2019 02:47:01 +0200 (CEST) Received: (qmail 7455 invoked by uid 500); 2 Apr 2019 00:47:01 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 7442 invoked by uid 99); 2 Apr 2019 00:47:00 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Apr 2019 00:47:00 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 499DEE00C6 for ; Tue, 2 Apr 2019 00:47:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 07C5C24422 for ; Tue, 2 Apr 2019 00:47:00 +0000 (UTC) Date: Tue, 2 Apr 2019 00:47:00 +0000 (UTC) From: "bd2019us (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (PHOENIX-5224) Iteratively executing the same SQL query will greatly damage the performance MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-5224?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] bd2019us updated PHOENIX-5224: ------------------------------ Description:=20 Locations:=C2=A0 (1) phoenix-core/src/it/java/org/apache/phoenix/end2end/index/IndexRebuildI= ncrementDisableCountIT.java:170 (2)=C2=A0phoenix-core/src/it/java/org/apache/phoenix/tx/TxCheckpointIT.java= :108 (3)=C2=A0phoenix-core/src/it/java/org/apache/phoenix/end2end/DeleteIT.java:= 794,858 (4)=C2=A0phoenix-core/src/it/java/org/apache/phoenix/end2end/UpsertSelectAu= toCommitIT.java:240 (5)=C2=A0phoenix-core/src/it/java/org/apache/phoenix/end2end/DropTableIT.ja= va:35 At these locations, the java.sql.Statement is intensively used in a loop an= d executing the same SQL query, which will highly damage the performance of= database access. In such cases, java.sql.PreparedStatement should be used= =C2=A0to enable the database compiling the SQL command ahead of time, which= has a much better performance compared with Statement. was: Locations:=C2=A0 (1) phoenix-core/src/it/java/org/apache/phoenix/end2end/index/IndexRebuildI= ncrementDisableCountIT.java:170 (2) phoenix-queryserver/src/it/java/org/apache/phoenix/end2end/HttpParamImp= ersonationQueryServerIT.java:383 (3)=C2=A0phoenix-core/src/it/java/org/apache/phoenix/tx/TxCheckpointIT.java= :108 (4)=C2=A0phoenix-core/src/it/java/org/apache/phoenix/end2end/DeleteIT.java:= 794,858 (5)=C2=A0phoenix-core/src/it/java/org/apache/phoenix/end2end/UpsertSelectAu= toCommitIT.java:240 (6)=C2=A0phoenix-core/src/it/java/org/apache/phoenix/end2end/DropTableIT.ja= va:35 (7)=C2=A0phoenix-queryserver/src/it/java/org/apache/phoenix/end2end/SecureQ= ueryServerIT.java:297 At these locations, the java.sql.Statement is intensively used in a loop an= d executing the same SQL query, which will highly damage the performance of= database access. In such cases, java.sql.PreparedStatement should be used= =C2=A0to enable the database compiling the SQL command ahead of time, which= has a much better performance compared with Statement. > Iteratively executing the same SQL query will greatly damage the performa= nce > -------------------------------------------------------------------------= --- > > Key: PHOENIX-5224 > URL: https://issues.apache.org/jira/browse/PHOENIX-5224 > Project: Phoenix > Issue Type: Bug > Reporter: bd2019us > Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Locations:=C2=A0 > (1) phoenix-core/src/it/java/org/apache/phoenix/end2end/index/IndexRebuil= dIncrementDisableCountIT.java:170 > (2)=C2=A0phoenix-core/src/it/java/org/apache/phoenix/tx/TxCheckpointIT.ja= va:108 > (3)=C2=A0phoenix-core/src/it/java/org/apache/phoenix/end2end/DeleteIT.jav= a:794,858 > (4)=C2=A0phoenix-core/src/it/java/org/apache/phoenix/end2end/UpsertSelect= AutoCommitIT.java:240 > (5)=C2=A0phoenix-core/src/it/java/org/apache/phoenix/end2end/DropTableIT.= java:35 > 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 use= d=C2=A0to enable the database compiling the SQL command ahead of time, whic= h has a much better performance compared with Statement. -- This message was sent by Atlassian JIRA (v7.6.3#76005)