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