[ http://issues.apache.org/jira/browse/DERBY-959?page=all ]
Sunitha Kambhampati updated DERBY-959:
--------------------------------------
Attachment: 959Notes_v1.html
derby959.review.diff.txt
derby959.review.stat.txt
I am attaching a patch 'derby959.review.diff.txt' to get feedback on the server
changes to allow for query block size greater than 32k. From the test cases
that I tried, it seems to me that the server already knows how to handle
sending QRYDTA greater than 32k.
Please see the attached html file 959Notes_v1.html for more notes:
This is a network server only change and I ran the derbynetclientmats and
derbynetmats with 1.4.2 sun jvm OK on windows.
I'd appreciate your comments and feedback.
Thanks.
> 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.2.0.0, 10.1.1.0, 10.1.1.1, 10.1.1.2
> Reporter: Bryan Pendleton
> Priority: Minor
> Attachments: 959Notes_v1.html, derby959.review.diff.txt,
> derby959.review.stat.txt
>
> 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
