[
https://issues.apache.org/jira/browse/DERBY-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen closed DERBY-3619.
-------------------------------------
Resolution: Fixed
Fix Version/s: 10.5.0.0
I'm not planning to add more test clients for now, so I'm closing this issue.
Most of Olav's nightly performance regression tests
(http://home.online.no/~olmsan/derby/perf/) now use
org.apache.derbyTesting.perf.clients.Runner. The only exceptions are the insert
and delete tests, as they don't really fit into the model used by Runner. For
instance, the delete tests quickly run out of rows to delete and must stop,
whereas Runner expects the test to go on for a certain amount of time. Similar
issues with insert when the table is full.
(It doesn't look like the graphs on Olav's site have been updated since
January, but I know the tests are still running each night. Will look into
that.)
> 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
> Fix For: 10.5.0.0
>
> 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.
