[ http://issues.apache.org/jira/browse/DERBY-1535?page=all ]
Tomohito Nakayama updated DERBY-1535:
-------------------------------------
Attachment: DERBY-1513_1535.patch
serverMemoryUsage_1513_1535.xls
I applied patch of both DERBY-1513(Trial-1) and DERBY-1535(Trial-2).
With this patch, OutOfMemoryError did not happen at NetworkServer in the
configuration of -Xms32m -Xmx128m.
//However , OutOfMemoryError happened at the Client....
There *were* different in the measured result from the referential result in
DERBY-1504, though it was not clear whether memory usage was improved ...
At least, the result shows that behavior of memory usage is different from
before.
//In my view, it seems like that chart of memory usage is more healthy than
before .....
I think this patch would improve memory usagein NetworkServer to some
extent.....
> 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-1513_1535.patch, DERBY-1535.patch,
> serverMemoryUsage.xls, serverMemoryUsage_1513_1535.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
