[
https://issues.apache.org/jira/browse/DERBY-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-3619:
--------------------------------------
Attachment: no-pk.diff
The attached patch (no-pk.diff) adds some more variants of the sr_select and
sr_update load types:
- sr_update can now operate on a CLOB or a BLOB column instead of a VARCHAR
column, just like sr_select
- sr_select and sr_update can now be told to pick out the row by a
non-indexed integer column or a column with a non-unique index instead of the
primary key column
I updated the help text printed by perf.clients.Runner to explain how to modify
the load. If you're running sr_select or sr_update and add "-load_opts
blob,nonIndexed" to the command line, the load is changed so that it
retrieves/updates blobs instead of varchars and selects rows by the non-indexed
column instead of the primary key column.
> 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.
