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 "Peter Schi (JIRA)" <ji...@apache.org> on 2008/06/06 05:02:45 UTC
[jira] Created: (DERBY-3713) memory leak when insert rows into a
table using org.apache.derby.jdbc.EmbeddedDriver
memory leak when insert rows into a table using org.apache.derby.jdbc.EmbeddedDriver
-------------------------------------------------------------------------------------
Key: DERBY-3713
URL: https://issues.apache.org/jira/browse/DERBY-3713
Project: Derby
Issue Type: Bug
Components: JDBC
Affects Versions: 10.4.1.3
Environment: solaris and macos, jdk1.5
Reporter: Peter Schi
Priority: Critical
I downloaded the latest derby and I only modified the SimpleApp.java which came with the software under db-derby-10.4.1.3-bin/demo/programs/simple directory by inserting a larger string into the same table and I inserted the same data for 10000 times, just using the default driver which was org.apache.derby.jdbc.EmbeddedDriver
I found out that there was memory leak, the size of used memory got increased and was about the same size of total data inserted into the table.
For example, if 2MB size of data was inserted into the table, then the size of used memory was increased by 2MB as well.
The memory leak still happened even if the database was shut down.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3713) memory leak when insert rows into a
table using org.apache.derby.jdbc.EmbeddedDriver
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602897#action_12602897 ]
Bryan Pendleton commented on DERBY-3713:
----------------------------------------
Due to the presence of page and record caches, the Derby memory usage will
tend to grow initially, until the cache is filled, at which point the memory usage
will level out and stabilize.
You can control the size of the cache with Derby system properties.
More information about memory usage, and about controlling the cache size,
is provided in the Derby documentation.
> memory leak when insert rows into a table using org.apache.derby.jdbc.EmbeddedDriver
> -------------------------------------------------------------------------------------
>
> Key: DERBY-3713
> URL: https://issues.apache.org/jira/browse/DERBY-3713
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.1.3
> Environment: solaris and macos, jdk1.5
> Reporter: Peter Schi
> Priority: Critical
>
> I downloaded the latest derby and I only modified the SimpleApp.java which came with the software under db-derby-10.4.1.3-bin/demo/programs/simple directory by inserting a larger string into the same table and I inserted the same data for 10000 times, just using the default driver which was org.apache.derby.jdbc.EmbeddedDriver
> I found out that there was memory leak, the size of used memory got increased and was about the same size of total data inserted into the table.
> For example, if 2MB size of data was inserted into the table, then the size of used memory was increased by 2MB as well.
> The memory leak still happened even if the database was shut down.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3713) memory leak when insert rows into a
table using org.apache.derby.jdbc.EmbeddedDriver
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644150#action_12644150 ]
Dag H. Wanvik commented on DERBY-3713:
--------------------------------------
I think so; the original author hasn't commented on Bryan's obervation, so
it's unclear if this is a bug at all and no repro exists.
> memory leak when insert rows into a table using org.apache.derby.jdbc.EmbeddedDriver
> -------------------------------------------------------------------------------------
>
> Key: DERBY-3713
> URL: https://issues.apache.org/jira/browse/DERBY-3713
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.1.3
> Environment: solaris and macos, jdk1.5
> Reporter: Peter Schi
>
> I downloaded the latest derby and I only modified the SimpleApp.java which came with the software under db-derby-10.4.1.3-bin/demo/programs/simple directory by inserting a larger string into the same table and I inserted the same data for 10000 times, just using the default driver which was org.apache.derby.jdbc.EmbeddedDriver
> I found out that there was memory leak, the size of used memory got increased and was about the same size of total data inserted into the table.
> For example, if 2MB size of data was inserted into the table, then the size of used memory was increased by 2MB as well.
> The memory leak still happened even if the database was shut down.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3713) memory leak when insert rows into a
table using org.apache.derby.jdbc.EmbeddedDriver
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644110#action_12644110 ]
Kathey Marsden commented on DERBY-3713:
---------------------------------------
Should this issue be closed invalid assuming that the normal cache growth is the issue?
> memory leak when insert rows into a table using org.apache.derby.jdbc.EmbeddedDriver
> -------------------------------------------------------------------------------------
>
> Key: DERBY-3713
> URL: https://issues.apache.org/jira/browse/DERBY-3713
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.1.3
> Environment: solaris and macos, jdk1.5
> Reporter: Peter Schi
>
> I downloaded the latest derby and I only modified the SimpleApp.java which came with the software under db-derby-10.4.1.3-bin/demo/programs/simple directory by inserting a larger string into the same table and I inserted the same data for 10000 times, just using the default driver which was org.apache.derby.jdbc.EmbeddedDriver
> I found out that there was memory leak, the size of used memory got increased and was about the same size of total data inserted into the table.
> For example, if 2MB size of data was inserted into the table, then the size of used memory was increased by 2MB as well.
> The memory leak still happened even if the database was shut down.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3713) memory leak when insert rows into a
table using org.apache.derby.jdbc.EmbeddedDriver
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-3713:
---------------------------------
Priority: Major (was: Critical)
Urgency: Normal (was: Urgent)
I am downgrading the urgency and priority of this JIRA because, as Bryan notes, the behavior seems to be what we expect and the behavior can be adjusted by tuning Derby properties.
> memory leak when insert rows into a table using org.apache.derby.jdbc.EmbeddedDriver
> -------------------------------------------------------------------------------------
>
> Key: DERBY-3713
> URL: https://issues.apache.org/jira/browse/DERBY-3713
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.1.3
> Environment: solaris and macos, jdk1.5
> Reporter: Peter Schi
>
> I downloaded the latest derby and I only modified the SimpleApp.java which came with the software under db-derby-10.4.1.3-bin/demo/programs/simple directory by inserting a larger string into the same table and I inserted the same data for 10000 times, just using the default driver which was org.apache.derby.jdbc.EmbeddedDriver
> I found out that there was memory leak, the size of used memory got increased and was about the same size of total data inserted into the table.
> For example, if 2MB size of data was inserted into the table, then the size of used memory was increased by 2MB as well.
> The memory leak still happened even if the database was shut down.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-3713) memory leak when insert rows into a
table using org.apache.derby.jdbc.EmbeddedDriver
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-3713.
-----------------------------------
Resolution: Invalid
It appears the user is seeing normal cache growth. If this proves not to be the case and we can get a reproduction, the issue can be reopened.
> memory leak when insert rows into a table using org.apache.derby.jdbc.EmbeddedDriver
> -------------------------------------------------------------------------------------
>
> Key: DERBY-3713
> URL: https://issues.apache.org/jira/browse/DERBY-3713
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.1.3
> Environment: solaris and macos, jdk1.5
> Reporter: Peter Schi
>
> I downloaded the latest derby and I only modified the SimpleApp.java which came with the software under db-derby-10.4.1.3-bin/demo/programs/simple directory by inserting a larger string into the same table and I inserted the same data for 10000 times, just using the default driver which was org.apache.derby.jdbc.EmbeddedDriver
> I found out that there was memory leak, the size of used memory got increased and was about the same size of total data inserted into the table.
> For example, if 2MB size of data was inserted into the table, then the size of used memory was increased by 2MB as well.
> The memory leak still happened even if the database was shut down.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.