From torque-dev-return-6898-apmail-db-torque-dev-archive=db.apache.org@db.apache.org Thu Jun 22 08:11:56 2006 Return-Path: Delivered-To: apmail-db-torque-dev-archive@www.apache.org Received: (qmail 79955 invoked from network); 22 Jun 2006 08:11:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Jun 2006 08:11:56 -0000 Received: (qmail 50707 invoked by uid 500); 22 Jun 2006 08:11:56 -0000 Delivered-To: apmail-db-torque-dev-archive@db.apache.org Received: (qmail 50692 invoked by uid 500); 22 Jun 2006 08:11:56 -0000 Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Apache Torque Developers List" Reply-To: "Apache Torque Developers List" Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 50676 invoked by uid 99); 22 Jun 2006 08:11:56 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2006 01:11:55 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2006 01:11:55 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C76C27141E6 for ; Thu, 22 Jun 2006 08:10:29 +0000 (GMT) Message-ID: <7436832.1150963829786.JavaMail.jira@brutus> Date: Thu, 22 Jun 2006 08:10:29 +0000 (GMT+00:00) From: "Joe Carter (JIRA)" To: torque-dev@db.apache.org Subject: [jira] Created: (TORQUE-36) Select performance problem with Sybase MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Select performance problem with Sybase -------------------------------------- Key: TORQUE-36 URL: http://issues.apache.org/jira/browse/TORQUE-36 Project: Torque Type: Bug Components: Runtime Versions: 3.2 Environment: Java 1.4.2 on solaris 10 against Sybase 12.5.2 Reporter: Joe Carter Selects via Torque perform 2-3 times slower than when doing the identical statement via JDBC. I took the SQL produced by Torque using p6spy to capture it. I manually implemented the same SQL as a raw query and a prepared statement obtaining a SQL connection from Torque.getConnection() to eliminate any differences in the pooling etc. I then ran performance tests against the 3 types. The ratio in performance (big is slower) was 10-4-3 for standard Torque, raw and then prepared statements. The performance hit was definately against the database as we're seeing similar performance improvements on production systems with the database CPU usage dropping dramatically with some gains on the calling tomcat server. The suspicion is that metadata is being retrieved on every select but p6spy unfortunately does not support the reporting of this so this cannot be confirmed. Note that the tests were performed without p6spy in the loop. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org For additional commands, e-mail: torque-dev-help@db.apache.org