[
https://issues.apache.org/jira/browse/DERBY-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-1442:
--------------------------------------
Urgency: Normal
Labels: derby_triage10_8 (was: )
> Do performance analysis and come up with a good query block size value for
> the client to send to the server
> -----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1442
> URL: https://issues.apache.org/jira/browse/DERBY-1442
> Project: Derby
> Issue Type: Improvement
> Components: Network Client, Network Server, Test
> Reporter: Sunitha Kambhampati
> Priority: Minor
> Labels: derby_triage10_8
>
> Do performance analysis, and find a good query block size value for the
> client to send to the server . Need to understand the memory usage also for
> greater query block size values.
> This issue is related to DERBY-959 and DERBY-1441.
> DERBY-959 has server side changes
> DERBY-1441 issue talks about client side changes
> DERBY-959 talks about 'Allowing use of QRYDTA block sizes greater than 32k'.
> As part of discussion on that jira, it was suggested that the performance
> analysis to decide a good query block size value for the client to send to
> the server be a separate task.
> Here is the link to the discussion that happened for DERBY-959.
> http://www.nabble.com/-jira--Created%3A-%28DERBY-959%29-Allow-use-of-DRDA-QRYDTA-block-sizes-greater-than-32K-t1106974.html#a2892273
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
