You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org> on 2006/07/25 20:59:15 UTC
[jira] Updated: (DERBY-1442) Do performance analysis and come up
with a good query block size value for the client to send to the server
[ http://issues.apache.org/jira/browse/DERBY-1442?page=all ]
Sunitha Kambhampati updated DERBY-1442:
---------------------------------------
Fix Version/s: (was: 10.2.0.0)
This is a good improvement, but since noone is assigned to it, changing fixin from 10.2 to unknown.
> 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: http://issues.apache.org/jira/browse/DERBY-1442
> Project: Derby
> Issue Type: Improvement
> Components: Network Server, Test, Network Client, Performance
> Reporter: Sunitha Kambhampati
> Priority: Minor
>
> 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.
-
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