[DERBY-1442] Do performance analysis and come up with a good query block size value for the client to send to the server

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: Network Client, Network Server, Test
• Labels: derby_triage10_8
• Urgency: Normal
• Bug behavior facts: Performance
• Assignee: Unassigned
• Reporter: Sunitha Kambhampati
• Created: 23/Jun/06 04:02
• Updated: 17/Feb/11 22:02

Description

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

Issue Links

• relates to: DERBY-1441 Allow client to be able to send greater than 32k query block size.
• relates to: DERBY-959 Allow use of DRDA QRYDTA block sizes greater than 32K