[ http://issues.apache.org/jira/browse/DERBY-1535?page=all ]
Tomohito Nakayama updated DERBY-1535:
-------------------------------------
Attachment: DERBY-1535.patch
serverMemoryUsage.xls
Reading the code of NetworkServer, it was found that PreparedStatement.setBytes
was used.
Here, I hypothesize that PreparedStatement.setBytes needs more memory than
PreparedStatement.setBinaryInputStream.
Based on that hypothesis, I change call of PreparedStatement.setBytes to
PreparedStatement.setBinaryInputStream.
Measured result was not different from referential result in DERBY-1504.
However, with this patch, OutOfMemoryError was not thrown from NetworkServer in
the configuration of -Xmx256m.
Without this patch, OutOfMemoryError was found in the same configuration of
-Xmx256m as written in
http://issues.apache.org/jira/browse/DERBY-1513#action_12421379.
// However again, OutOfMemoryError happened at the client side....
// But it is not at server side.
> Trial2 for DERBY-550, improve use of Engine from NetworkServer and reduce
> memory usage
> --------------------------------------------------------------------------------------
>
> Key: DERBY-1535
> URL: http://issues.apache.org/jira/browse/DERBY-1535
> Project: Derby
> Issue Type: Sub-task
> Reporter: Tomohito Nakayama
> Attachments: DERBY-1535.patch, serverMemoryUsage.xls
>
>
> Through DERBY-1513, Trial 1 for DERBY-550,
> it was suggested that NetworkServer seems to use Engine inefficiently and use
> too much of memory.
> This task try to improve the use of Engine from NetworkServer and try to
> reduce memory usage.
--
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
