Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 62818 invoked from network); 22 Jun 2006 22:15:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Jun 2006 22:15:59 -0000 Received: (qmail 85244 invoked by uid 500); 22 Jun 2006 22:15:58 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 85220 invoked by uid 500); 22 Jun 2006 22:15:58 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 85211 invoked by uid 99); 22 Jun 2006 22:15:57 -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 15:15:57 -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 15:15:57 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 951E3410008 for ; Thu, 22 Jun 2006 22:14:30 +0000 (GMT) Message-ID: <14810211.1151014470608.JavaMail.jira@brutus> Date: Thu, 22 Jun 2006 22:14:30 +0000 (GMT+00:00) From: "Mike Matrigali (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-959) Allow use of DRDA QRYDTA block sizes greater than 32K In-Reply-To: <506158573.1139711968116.JavaMail.jira@ajax.apache.org> 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 [ http://issues.apache.org/jira/browse/DERBY-959?page=all ] Mike Matrigali updated DERBY-959: --------------------------------- Fix Version: 10.2.0.0 I committed the xxx patch to the trunk: m1_142:151>svn commit Sending java\drda\org\apache\derby\impl\drda\CodePoint.java Sending java\testing\org\apache\derbyTesting\functionTests\master\testProtocol.out Sending java\testing\org\apache\derbyTesting\functionTests\tests\derbynet\protocol.tests Sending java\testing\org\apache\derbyTesting\functionTests\tests\derbynet\testProtocol_app.properties Transmitting file data .... Committed revision 416485. > Allow use of DRDA QRYDTA block sizes greater than 32K > ----------------------------------------------------- > > Key: DERBY-959 > URL: http://issues.apache.org/jira/browse/DERBY-959 > Project: Derby > Type: Improvement > Components: Network Client, Performance, Network Server > Versions: 10.1.1.0, 10.2.0.0, 10.1.1.1, 10.1.1.2 > Reporter: Bryan Pendleton > Priority: Minor > Fix For: 10.2.0.0 > Attachments: 959Notes_v1.html, SmallRows_32kBlkSz.trace, SmallRows_64kBlkSz.trace, derby959.review.diff.txt, derby959.review.stat.txt, odbc_rowgreaterthan64k.trace > > Currently, the Network Server and Network Client use a 32K blocksize when > returning database data in QRYDTA blocks. > I came across the following statement in the DRDA spec (Volume 1, page 12): > Blocking applies only to the QRYDTA reply objects. Each > query block is a QRYDTA DSS. The maximum query block size > value allowed in the qryblksz parameter is increased from > 32K to 10M, thus accomodating the larger data volumes > required by modern, more data-intensive applications. > The importance of larger block sizes depends strong on the application > profile.. For example, many applications perform single-record selects, > and they are not influenced by the block size. > But for some applications, it seems like the ability to use a larger block > size could be quite valuable. -- 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