|

»

Memory usage version 1.9

View: New views

4 Messages — Rating Filter: Alert me

	Memory usage version 1.9 by Rob Gansevles :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hello, Thanks for the quick fixes of the 4 issues I raised, these were causing our system tests to fail, they now all work. Is the memory usage of the 1.9 driver different from 1.8? Since I replaced the driver our automatic test environment bombs out with out-of-memory error (i have not looked at the jvm settings yet). These tests are all quite simple, they create only a very few small tables and run some sql agains them. Is there any guideline about preferred memory settings for hsql 1.9? Rob ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Hsqldb-user mailing list Hsqldb-user@... https://lists.sourceforge.net/lists/listinfo/hsqldb-user
	Re: Memory usage version 1.9 by Fred Toussi-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Not in my tests. I run the TestSelf suite of SQL scripts with -Xmx11M. I can reduce it to 7M if I exclude the TestSelfSysTables.txt. This suite is run by org.hsqldb.test.TestSelf and the scripts are in the /testrun/hsqldb/ directory of the zip and SVN. You may have found something that is marginal, which you can ignore, or a specific statement that is not working correctly, which we can fix. Please run with 1.8 with reduced Xmx until you find the minimum required memory, then with 1.9 with increased Xmx and let me know the results. Fred ----- Original Message ----- From: rgansevles@... To: hsqldb-user@... Sent: 10 October 2009 14:01 Subject: [Hsqldb-user] Memory usage version 1.9 Hello, Thanks for the quick fixes of the 4 issues I raised, these were causing our system tests to fail, they now all work. Is the memory usage of the 1.9 driver different from 1.8? Since I replaced the driver our automatic test environment bombs out with out-of-memory error (i have not looked at the jvm settings yet). These tests are all quite simple, they create only a very few small tables and run some sql agains them. Is there any guideline about preferred memory settings for hsql 1.9? Rob ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Hsqldb-user mailing list Hsqldb-user@... https://lists.sourceforge.net/lists/listinfo/hsqldb-user ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Hsqldb-user mailing list Hsqldb-user@... https://lists.sourceforge.net/lists/listinfo/hsqldb-user
	Re: Memory usage version 1.9 by Rob Gansevles :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Fred, I did not see any big memory difference between 1.8 and 1.9, but it appeared not to be the issue. My problem is a deadlock in our system on the hsql driver. It seems that a select issued in 1 connection (autoCommit=false) keeps a lock on the table even if the select is completely processed (it does not have any results in our case). An insert executed from another connection blocks on the select statement. I will create an issue and attach a sample program. The program executes fine with the 1.8 driver and hangs with the 1.9 driver. Rob On Sat, Oct 10, 2009 at 3:29 PM, fredt <fredt@...> wrote: Not in my tests. I run the TestSelf suite of SQL scripts with -Xmx11M. I can reduce it to 7M if I exclude the TestSelfSysTables.txt. This suite is run by org.hsqldb.test.TestSelf and the scripts are in the /testrun/hsqldb/ directory of the zip and SVN. You may have found something that is marginal, which you can ignore, or a specific statement that is not working correctly, which we can fix. Please run with 1.8 with reduced Xmx until you find the minimum required memory, then with 1.9 with increased Xmx and let me know the results. Fred ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Hsqldb-user mailing list Hsqldb-user@... https://lists.sourceforge.net/lists/listinfo/hsqldb-user
	Re: Memory usage version 1.9 by Fred Toussi-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. If your connection is not auto commit, then this is currently by design. If it is in auto commit, then the lock should be removed and it is an issue. I will be changing the default behaviour so that read locks are removed in the default mode even when not in auto commit. Fred On Wed, 28 Oct 2009 12:38 +0100, "Rob Gansevles" <rgansevles@...> wrote: Fred, I did not see any big memory difference between 1.8 and 1.9, but it appeared not to be the issue. My problem is a deadlock in our system on the hsql driver. It seems that a select issued in 1 connection (autoCommit=false) keeps a lock on the table even if the select is completely processed (it does not have any results in our case). An insert executed from another connection blocks on the select statement. I will create an issue and attach a sample program. The program executes fine with the 1.8 driver and hangs with the 1.9 driver. Rob On Sat, Oct 10, 2009 at 3:29 PM, fredt <fredt@...> wrote: Not in my tests. I run the TestSelf suite of SQL scripts with -Xmx11M. I can reduce it to 7M if I exclude the TestSelfSysTables.txt. This suite is run by org.hsqldb.test.TestSelf and the scripts are in the /testrun/hsqldb/ directory of the zip and SVN. You may have found something that is marginal, which you can ignore, or a specific statement that is not working correctly, which we can fix. Please run with 1.8 with reduced Xmx until you find the minimum required memory, then with 1.9 with increased Xmx and let me know the results. Fred ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Hsqldb-user mailing list Hsqldb-user@... https://lists.sourceforge.net/lists/listinfo/hsqldb-user