You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Milosz Tylenda (JIRA)" <ji...@apache.org> on 2010/11/07 18:58:06 UTC
[jira] Created: (OPENJPA-1876) Slow JDBC tests
Slow JDBC tests
---------------
Key: OPENJPA-1876
URL: https://issues.apache.org/jira/browse/OPENJPA-1876
Project: OpenJPA
Issue Type: Bug
Affects Versions: 2.1.0
Reporter: Milosz Tylenda
Persistence JDBC tests and other database connected tests have been suffering from slow down starting somewhere in September 2010 [1]. I can see this in my environment as well as Hudson builds:
OpenJPA-trunk-deploy: Build #49 (Nov 7, 2010 6:46:34 AM): OpenJPA Persistence JDBC: 34 min
OpenJPA-20x-deploy: Build #23 (Nov 5, 2010 7:14:48 PM): OpenJPA Persistence JDBC: 10 min
As seen above, the trunk build executes much slower than the 2.0.x build yet the number of tests is roughly the same and there are no significant differences in execution times of modules that do not touch database.
[1] http://openjpa.208410.n2.nabble.com/Slow-JDBC-test-suite-tp5594040p5594040.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-1876) Slow JDBC tests
Posted by "Milosz Tylenda (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932880#action_12932880 ]
Milosz Tylenda commented on OPENJPA-1876:
-----------------------------------------
Hi Rick. These are indeed the longest ones but in fact all database related tests are gradually slowed down.
It might be related either to derby test profile or derby itself, since when I run the tests against another database, there is no slowdown.
> Slow JDBC tests
> ---------------
>
> Key: OPENJPA-1876
> URL: https://issues.apache.org/jira/browse/OPENJPA-1876
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Milosz Tylenda
>
> Persistence JDBC tests and other database connected tests have been suffering from slow down starting somewhere in September 2010 [1]. I can see this in my environment as well as Hudson builds:
> OpenJPA-trunk-deploy: Build #49 (Nov 7, 2010 6:46:34 AM): OpenJPA Persistence JDBC: 34 min
> OpenJPA-20x-deploy: Build #23 (Nov 5, 2010 7:14:48 PM): OpenJPA Persistence JDBC: 10 min
> As seen above, the trunk build executes much slower than the 2.0.x build yet the number of tests is roughly the same and there are no significant differences in execution times of modules that do not touch database.
> [1] http://openjpa.208410.n2.nabble.com/Slow-JDBC-test-suite-tp5594040p5594040.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-1876) Slow JDBC tests
Posted by "Rick Curtis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932598#action_12932598 ]
Rick Curtis commented on OPENJPA-1876:
--------------------------------------
I looked at which tests are taking a long time this afternoon and came up with this list ... these are all 10+ seconds. I'm not sure which of these can be attributed to the 'problem' tests, but they are the longest running.
Name Duration Tests
TestClearableScheduler (org.apache.openjpa.persistence.datacache) 3m:01s,088ms 1
TestQueryTimeout (org.apache.openjpa.persistence.query) 49s,306ms 12
TestDaytrader (org.apache.openjpa.integration.daytrader) 42s,167ms 1
TestTimeoutException (org.apache.openjpa.persistence.query) 30s,222ms 3
TestSJVMCache (org.apache.openjpa.persistence.datacache) 24s,390ms 30
TestDataCachePCDataGenerator (org.apache.openjpa.persistence.datacache) 23s,567ms 30
TestTypesafeCriteria (org.apache.openjpa.persistence.criteria) 22s,802ms 100
TestEnhancementWithMultiplePUs (org.apache.openjpa.enhance) 18s,864ms 3
TestJPQLSubquery (org.apache.openjpa.persistence.criteria) 14s,346ms 59
TestTypeSafeCondExpression (org.apache.openjpa.persistence.criteria) 13s,267ms 55
TestEmbeddable (org.apache.openjpa.persistence.embed) 10s,862ms 26
> Slow JDBC tests
> ---------------
>
> Key: OPENJPA-1876
> URL: https://issues.apache.org/jira/browse/OPENJPA-1876
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Milosz Tylenda
>
> Persistence JDBC tests and other database connected tests have been suffering from slow down starting somewhere in September 2010 [1]. I can see this in my environment as well as Hudson builds:
> OpenJPA-trunk-deploy: Build #49 (Nov 7, 2010 6:46:34 AM): OpenJPA Persistence JDBC: 34 min
> OpenJPA-20x-deploy: Build #23 (Nov 5, 2010 7:14:48 PM): OpenJPA Persistence JDBC: 10 min
> As seen above, the trunk build executes much slower than the 2.0.x build yet the number of tests is roughly the same and there are no significant differences in execution times of modules that do not touch database.
> [1] http://openjpa.208410.n2.nabble.com/Slow-JDBC-test-suite-tp5594040p5594040.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-1876) Slow JDBC tests
Posted by "Milosz Tylenda (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982619#action_12982619 ]
Milosz Tylenda commented on OPENJPA-1876:
-----------------------------------------
Narrowing further, the issue happens because we set connection properties (e.g. JDBC driver class) in the main pom.xml differently after implementing DBCP pooling auto-enablement. This impacts automatic Derby shutdown when closing a data source. Although we have always had set DerbyDictionary.shutdownOnClose set to true, we were not shutting Derby down in our tests. After the properties changed, we started doing the shutdown and this is slowing DELETE statements (but why?). It looks like the shutdown might be a good option for user applications but not for unit tests. Setting DerbyDictionary.shutdownOnClose=false should resolve the issue.
As for the lack of database and driver version message in the log, it is also caused by the properties change. However, it is quite a good thing here - it means OpenJPA is able to figure out DBDictionary class without connecting to the database.
> Slow JDBC tests
> ---------------
>
> Key: OPENJPA-1876
> URL: https://issues.apache.org/jira/browse/OPENJPA-1876
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Milosz Tylenda
> Assignee: Milosz Tylenda
>
> Persistence JDBC tests and other database connected tests have been suffering from slow down starting somewhere in September 2010 [1]. I can see this in my environment as well as Hudson builds:
> OpenJPA-trunk-deploy: Build #49 (Nov 7, 2010 6:46:34 AM): OpenJPA Persistence JDBC: 34 min
> OpenJPA-20x-deploy: Build #23 (Nov 5, 2010 7:14:48 PM): OpenJPA Persistence JDBC: 10 min
> As seen above, the trunk build executes much slower than the 2.0.x build yet the number of tests is roughly the same and there are no significant differences in execution times of modules that do not touch database.
> [1] http://openjpa.208410.n2.nabble.com/Slow-JDBC-test-suite-tp5594040p5594040.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-1876) Slow JDBC tests
Posted by "Milosz Tylenda (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Milosz Tylenda resolved OPENJPA-1876.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
> Slow JDBC tests
> ---------------
>
> Key: OPENJPA-1876
> URL: https://issues.apache.org/jira/browse/OPENJPA-1876
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Milosz Tylenda
> Assignee: Milosz Tylenda
> Fix For: 2.2.0
>
>
> Persistence JDBC tests and other database connected tests have been suffering from slow down starting somewhere in September 2010 [1]. I can see this in my environment as well as Hudson builds:
> OpenJPA-trunk-deploy: Build #49 (Nov 7, 2010 6:46:34 AM): OpenJPA Persistence JDBC: 34 min
> OpenJPA-20x-deploy: Build #23 (Nov 5, 2010 7:14:48 PM): OpenJPA Persistence JDBC: 10 min
> As seen above, the trunk build executes much slower than the 2.0.x build yet the number of tests is roughly the same and there are no significant differences in execution times of modules that do not touch database.
> [1] http://openjpa.208410.n2.nabble.com/Slow-JDBC-test-suite-tp5594040p5594040.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Closed] (OPENJPA-1876) Slow JDBC tests
Posted by "Albert Lee (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee closed OPENJPA-1876.
-------------------------------
Close issue in preparation for 2.2.0 release.
> Slow JDBC tests
> ---------------
>
> Key: OPENJPA-1876
> URL: https://issues.apache.org/jira/browse/OPENJPA-1876
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Milosz Tylenda
> Assignee: Milosz Tylenda
> Fix For: 2.2.0
>
>
> Persistence JDBC tests and other database connected tests have been suffering from slow down starting somewhere in September 2010 [1]. I can see this in my environment as well as Hudson builds:
> OpenJPA-trunk-deploy: Build #49 (Nov 7, 2010 6:46:34 AM): OpenJPA Persistence JDBC: 34 min
> OpenJPA-20x-deploy: Build #23 (Nov 5, 2010 7:14:48 PM): OpenJPA Persistence JDBC: 10 min
> As seen above, the trunk build executes much slower than the 2.0.x build yet the number of tests is roughly the same and there are no significant differences in execution times of modules that do not touch database.
> [1] http://openjpa.208410.n2.nabble.com/Slow-JDBC-test-suite-tp5594040p5594040.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (OPENJPA-1876) Slow JDBC tests
Posted by "Milosz Tylenda (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Milosz Tylenda reassigned OPENJPA-1876:
---------------------------------------
Assignee: Milosz Tylenda
> Slow JDBC tests
> ---------------
>
> Key: OPENJPA-1876
> URL: https://issues.apache.org/jira/browse/OPENJPA-1876
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Milosz Tylenda
> Assignee: Milosz Tylenda
>
> Persistence JDBC tests and other database connected tests have been suffering from slow down starting somewhere in September 2010 [1]. I can see this in my environment as well as Hudson builds:
> OpenJPA-trunk-deploy: Build #49 (Nov 7, 2010 6:46:34 AM): OpenJPA Persistence JDBC: 34 min
> OpenJPA-20x-deploy: Build #23 (Nov 5, 2010 7:14:48 PM): OpenJPA Persistence JDBC: 10 min
> As seen above, the trunk build executes much slower than the 2.0.x build yet the number of tests is roughly the same and there are no significant differences in execution times of modules that do not touch database.
> [1] http://openjpa.208410.n2.nabble.com/Slow-JDBC-test-suite-tp5594040p5594040.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (OPENJPA-1876) Slow JDBC tests
Posted by "Milosz Tylenda (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on OPENJPA-1876 started by Milosz Tylenda.
> Slow JDBC tests
> ---------------
>
> Key: OPENJPA-1876
> URL: https://issues.apache.org/jira/browse/OPENJPA-1876
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Milosz Tylenda
> Assignee: Milosz Tylenda
>
> Persistence JDBC tests and other database connected tests have been suffering from slow down starting somewhere in September 2010 [1]. I can see this in my environment as well as Hudson builds:
> OpenJPA-trunk-deploy: Build #49 (Nov 7, 2010 6:46:34 AM): OpenJPA Persistence JDBC: 34 min
> OpenJPA-20x-deploy: Build #23 (Nov 5, 2010 7:14:48 PM): OpenJPA Persistence JDBC: 10 min
> As seen above, the trunk build executes much slower than the 2.0.x build yet the number of tests is roughly the same and there are no significant differences in execution times of modules that do not touch database.
> [1] http://openjpa.208410.n2.nabble.com/Slow-JDBC-test-suite-tp5594040p5594040.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.