[jira] Commented: (DERBY-3619) Implement more load types for org.apache.derbyTesting.perf.clients.Runner
[ https://issues.apache.org/jira/browse/DERBY-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608763#action_12608763 ] Kristian Waagan commented on DERBY-3619: For what it's worth, I have tested the bank transaction client by using it as a benchmark to test the JDBC client side statement cache. No problems discovered. > Implement more load types for org.apache.derbyTesting.perf.clients.Runner > - > > Key: DERBY-3619 > URL: https://issues.apache.org/jira/browse/DERBY-3619 > Project: Derby > Issue Type: Test > Components: Performance >Reporter: Knut Anders Hatlen >Assignee: Knut Anders Hatlen >Priority: Minor > Attachments: bank-clients.diff, create-accounts.diff, lob.diff, > no-pk.diff, runner.diff > > > I'm planning to add some more load types to > org.apache.derbyTesting.perf.clients.Runner so that we can run tests whose > load is roughly equivalent to the tests run in Olav's nightly performance > regression tests - http://home.online.no/~olmsan/derby/perf/. Having such > tests available would make it easier to investigate performance regressions > reported by those test runs. Currently, we have clients under > o.a.dt.perf.clients that generate load that is similar to the single-record > select and single-record update operations with primary key and the primary > key join operations (in fact, the nightly regression tests have used the > tests in derbyTesting.jar for these types of load for about a month now). > For the following types of load, we don't have test clients in > derbyTesting.jar: > 1) tests for insert performance > 2) tests for delete performance > 3) single-record select + single-record update on secondary index > 4) single-record select + single-record update on non-indexed column > 5) TPC-B like transactions (should probably be called something else, but I > think it's useful to have a test that uses the same schema and queries as > described in the TPC-B spec) > (3) and (4) are just variants over the existing single-record tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3619) Implement more load types for org.apache.derbyTesting.perf.clients.Runner
[ https://issues.apache.org/jira/browse/DERBY-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607889#action_12607889 ] Knut Anders Hatlen commented on DERBY-3619: --- Committed revision 671462 > Implement more load types for org.apache.derbyTesting.perf.clients.Runner > - > > Key: DERBY-3619 > URL: https://issues.apache.org/jira/browse/DERBY-3619 > Project: Derby > Issue Type: Test > Components: Performance >Reporter: Knut Anders Hatlen >Assignee: Knut Anders Hatlen >Priority: Minor > Attachments: bank-clients.diff, create-accounts.diff, lob.diff, > no-pk.diff > > > I'm planning to add some more load types to > org.apache.derbyTesting.perf.clients.Runner so that we can run tests whose > load is roughly equivalent to the tests run in Olav's nightly performance > regression tests - http://home.online.no/~olmsan/derby/perf/. Having such > tests available would make it easier to investigate performance regressions > reported by those test runs. Currently, we have clients under > o.a.dt.perf.clients that generate load that is similar to the single-record > select and single-record update operations with primary key and the primary > key join operations (in fact, the nightly regression tests have used the > tests in derbyTesting.jar for these types of load for about a month now). > For the following types of load, we don't have test clients in > derbyTesting.jar: > 1) tests for insert performance > 2) tests for delete performance > 3) single-record select + single-record update on secondary index > 4) single-record select + single-record update on non-indexed column > 5) TPC-B like transactions (should probably be called something else, but I > think it's useful to have a test that uses the same schema and queries as > described in the TPC-B spec) > (3) and (4) are just variants over the existing single-record tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3619) Implement more load types for org.apache.derbyTesting.perf.clients.Runner
[ https://issues.apache.org/jira/browse/DERBY-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598574#action_12598574 ] Knut Anders Hatlen commented on DERBY-3619: --- Committed revision 658572. > Implement more load types for org.apache.derbyTesting.perf.clients.Runner > - > > Key: DERBY-3619 > URL: https://issues.apache.org/jira/browse/DERBY-3619 > Project: Derby > Issue Type: Test > Components: Performance >Reporter: Knut Anders Hatlen >Assignee: Knut Anders Hatlen >Priority: Minor > Attachments: lob.diff, no-pk.diff > > > I'm planning to add some more load types to > org.apache.derbyTesting.perf.clients.Runner so that we can run tests whose > load is roughly equivalent to the tests run in Olav's nightly performance > regression tests - http://home.online.no/~olmsan/derby/perf/. Having such > tests available would make it easier to investigate performance regressions > reported by those test runs. Currently, we have clients under > o.a.dt.perf.clients that generate load that is similar to the single-record > select and single-record update operations with primary key and the primary > key join operations (in fact, the nightly regression tests have used the > tests in derbyTesting.jar for these types of load for about a month now). > For the following types of load, we don't have test clients in > derbyTesting.jar: > 1) tests for insert performance > 2) tests for delete performance > 3) single-record select + single-record update on secondary index > 4) single-record select + single-record update on non-indexed column > 5) TPC-B like transactions (should probably be called something else, but I > think it's useful to have a test that uses the same schema and queries as > described in the TPC-B spec) > (3) and (4) are just variants over the existing single-record tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3619) Implement more load types for org.apache.derbyTesting.perf.clients.Runner
[ https://issues.apache.org/jira/browse/DERBY-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591636#action_12591636 ] Knut Anders Hatlen commented on DERBY-3619: --- Now the CLOB test is part of the nightly regression suite and the results are published at http://home.online.no/~olmsan/derby/perf/. The test doesn't show the above mentioned regression (DERBY-3312), probably because the nightly regression tests run the clients on a different machine than the server. In fact, the tests show a ~50X speedup for the client/server test from 10.2.2.0 to the current trunk when running a single-threaded test. > Implement more load types for org.apache.derbyTesting.perf.clients.Runner > - > > Key: DERBY-3619 > URL: https://issues.apache.org/jira/browse/DERBY-3619 > Project: Derby > Issue Type: Test > Components: Performance >Reporter: Knut Anders Hatlen >Assignee: Knut Anders Hatlen >Priority: Minor > Attachments: lob.diff > > > I'm planning to add some more load types to > org.apache.derbyTesting.perf.clients.Runner so that we can run tests whose > load is roughly equivalent to the tests run in Olav's nightly performance > regression tests - http://home.online.no/~olmsan/derby/perf/. Having such > tests available would make it easier to investigate performance regressions > reported by those test runs. Currently, we have clients under > o.a.dt.perf.clients that generate load that is similar to the single-record > select and single-record update operations with primary key and the primary > key join operations (in fact, the nightly regression tests have used the > tests in derbyTesting.jar for these types of load for about a month now). > For the following types of load, we don't have test clients in > derbyTesting.jar: > 1) tests for insert performance > 2) tests for delete performance > 3) single-record select + single-record update on secondary index > 4) single-record select + single-record update on non-indexed column > 5) TPC-B like transactions (should probably be called something else, but I > think it's useful to have a test that uses the same schema and queries as > described in the TPC-B spec) > (3) and (4) are just variants over the existing single-record tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3619) Implement more load types for org.apache.derbyTesting.perf.clients.Runner
[ https://issues.apache.org/jira/browse/DERBY-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590894#action_12590894 ] Knut Anders Hatlen commented on DERBY-3619: --- Committed lob.diff with revision 650112. > Implement more load types for org.apache.derbyTesting.perf.clients.Runner > - > > Key: DERBY-3619 > URL: https://issues.apache.org/jira/browse/DERBY-3619 > Project: Derby > Issue Type: Test > Components: Performance >Reporter: Knut Anders Hatlen >Assignee: Knut Anders Hatlen >Priority: Minor > Attachments: lob.diff > > > I'm planning to add some more load types to > org.apache.derbyTesting.perf.clients.Runner so that we can run tests whose > load is roughly equivalent to the tests run in Olav's nightly performance > regression tests - http://home.online.no/~olmsan/derby/perf/. Having such > tests available would make it easier to investigate performance regressions > reported by those test runs. Currently, we have clients under > o.a.dt.perf.clients that generate load that is similar to the single-record > select and single-record update operations with primary key and the primary > key join operations (in fact, the nightly regression tests have used the > tests in derbyTesting.jar for these types of load for about a month now). > For the following types of load, we don't have test clients in > derbyTesting.jar: > 1) tests for insert performance > 2) tests for delete performance > 3) single-record select + single-record update on secondary index > 4) single-record select + single-record update on non-indexed column > 5) TPC-B like transactions (should probably be called something else, but I > think it's useful to have a test that uses the same schema and queries as > described in the TPC-B spec) > (3) and (4) are just variants over the existing single-record tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3619) Implement more load types for org.apache.derbyTesting.perf.clients.Runner
[ https://issues.apache.org/jira/browse/DERBY-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589558#action_12589558 ] Knut Anders Hatlen commented on DERBY-3619: --- The single-record tests that are currently checked in fetch or update strings with 100 characters. We could easily add an option to replace the strings with Clobs or Blobs. I'll try to do that and also see if I can squeeze in an extra test in the nightly runs. > Implement more load types for org.apache.derbyTesting.perf.clients.Runner > - > > Key: DERBY-3619 > URL: https://issues.apache.org/jira/browse/DERBY-3619 > Project: Derby > Issue Type: Test > Components: Performance >Reporter: Knut Anders Hatlen >Assignee: Knut Anders Hatlen >Priority: Minor > > I'm planning to add some more load types to > org.apache.derbyTesting.perf.clients.Runner so that we can run tests whose > load is roughly equivalent to the tests run in Olav's nightly performance > regression tests - http://home.online.no/~olmsan/derby/perf/. Having such > tests available would make it easier to investigate performance regressions > reported by those test runs. Currently, we have clients under > o.a.dt.perf.clients that generate load that is similar to the single-record > select and single-record update operations with primary key and the primary > key join operations (in fact, the nightly regression tests have used the > tests in derbyTesting.jar for these types of load for about a month now). > For the following types of load, we don't have test clients in > derbyTesting.jar: > 1) tests for insert performance > 2) tests for delete performance > 3) single-record select + single-record update on secondary index > 4) single-record select + single-record update on non-indexed column > 5) TPC-B like transactions (should probably be called something else, but I > think it's useful to have a test that uses the same schema and queries as > described in the TPC-B spec) > (3) and (4) are just variants over the existing single-record tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3619) Implement more load types for org.apache.derbyTesting.perf.clients.Runner
[ https://issues.apache.org/jira/browse/DERBY-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589128#action_12589128 ] Kathey Marsden commented on DERBY-3619: --- It would be good to have a performance sanity check for lobs. We have been regressing. See: https://issues.apache.org/jira/browse/DERBY-3312 > Implement more load types for org.apache.derbyTesting.perf.clients.Runner > - > > Key: DERBY-3619 > URL: https://issues.apache.org/jira/browse/DERBY-3619 > Project: Derby > Issue Type: Test > Components: Performance >Reporter: Knut Anders Hatlen >Assignee: Knut Anders Hatlen >Priority: Minor > > I'm planning to add some more load types to > org.apache.derbyTesting.perf.clients.Runner so that we can run tests whose > load is roughly equivalent to the tests run in Olav's nightly performance > regression tests - http://home.online.no/~olmsan/derby/perf/. Having such > tests available would make it easier to investigate performance regressions > reported by those test runs. Currently, we have clients under > o.a.dt.perf.clients that generate load that is similar to the single-record > select and single-record update operations with primary key and the primary > key join operations (in fact, the nightly regression tests have used the > tests in derbyTesting.jar for these types of load for about a month now). > For the following types of load, we don't have test clients in > derbyTesting.jar: > 1) tests for insert performance > 2) tests for delete performance > 3) single-record select + single-record update on secondary index > 4) single-record select + single-record update on non-indexed column > 5) TPC-B like transactions (should probably be called something else, but I > think it's useful to have a test that uses the same schema and queries as > described in the TPC-B spec) > (3) and (4) are just variants over the existing single-record tests. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
