[ http://issues.apache.org/jira/browse/DERBY-959?page=comments#action_12417367 ]
Sunitha Kambhampati commented on DERBY-959: ------------------------------------------- Discussion happened on this issue on derby-dev. Here is the link to the discussion that happened on derby-dev http://www.nabble.com/-jira--Created%3A-%28DERBY-959%29-Allow-use-of-DRDA-QRYDTA-block-sizes-greater-than-32K-t1106974.html#a2892273 I have opened two other jira issues for the tasks related to this issue. . DERBY-1441 - client side changes to support query block size greater than 32k DERBY-1442- to do performance analysis and come up with a 'good' query block size value for the client to send to the server. > 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 > 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
