You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2006/11/17 18:48:38 UTC
[jira] Created: (DERBY-2095) Add the ability to populate a database
for the order entry toolkit based upon the TPC-C specification.
Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
------------------------------------------------------------------------------------------------------
Key: DERBY-2095
URL: http://issues.apache.org/jira/browse/DERBY-2095
Project: Derby
Issue Type: Sub-task
Components: Test
Reporter: Daniel John Debrunner
Priority: Minor
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-2095) Add the ability to populate a database
for the order entry toolkit based upon the TPC-C specification.
Posted by "Sunitha Kambhampati (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunitha Kambhampati updated DERBY-2095:
---------------------------------------
Attachment: derby2095.p2.diff.txt
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: derby2095.p2.diff.txt, oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2095) Add the ability to populate a
database for the order entry toolkit based upon the TPC-C specification.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465627 ]
Daniel John Debrunner commented on DERBY-2095:
----------------------------------------------
I'll look at committing this.
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2095) Add the ability to populate a
database for the order entry toolkit based upon the TPC-C specification.
Posted by "Sunitha Kambhampati (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466200 ]
Sunitha Kambhampati commented on DERBY-2095:
--------------------------------------------
Thanks very much Dan for your review comments. I am glad you caught the 0 and 1 based inconsistency.
I am attaching a patch (derby2095.p2.diff.txt) that incorporates the review comments, cleanup, and also adds some tests for consistency checks.
Details are as follows:
1) Add a new class Checks. This class has fixtures to test for rowcounts, as well as the consistency checks mentioned in Section 3.3.2.1 to 3.3.2.4 of TPC-C specification.
2) Cleanup Load interface to remove the single table loads
3) Remove LoadTester as it is no longer needed
4) Push fixtures to test the rowcounts to the Checks class from the OETest.OETest as well as the Populate test call test fixtures from Checks class.
6) Remove SimpleInsert(Connection,short) constructor as it is no longer needed.
7) Changes in SimpleInsert to make all tables 1 based.
8) Add a new Test Class -Schema to load the schema and cleanup code in OETest and Populate.
Also note:
-- Now that OETest will call the Schema fixtures to run the test, there will be output printed on System.out for the performance response time numbers for the schema creation also.
-- With this set of cleanup, SimpleInsert object in setUp of Populate will only be created once, for the load test which is required.
__________________________
To run the test, its the same command as before. Now there will be 4 more tests run that includes the consistency conditions 1 to 4 if you enable the doChecks option.
Some e.g
//scale 1
java org.apache.derbyTesting.system.oe.run.Populate
java org.apache.derbyTesting.system.oe.run.Populate -scale 2 -doChecks false -createConstraintsBeforeLoad false
svn stat:
M java\testing\org\apache\derbyTesting\system\oe\load\SimpleInsert.java
M java\testing\org\apache\derbyTesting\system\oe\test\OETest.java
D java\testing\org\apache\derbyTesting\system\oe\test\LoadTester.java
A java\testing\org\apache\derbyTesting\system\oe\run\Checks.java
A java\testing\org\apache\derbyTesting\system\oe\run\Schema.java
M java\testing\org\apache\derbyTesting\system\oe\run\Populate.java
M java\testing\org\apache\derbyTesting\system\oe\client\Load.java
Can someone please review this patch. Thanks.
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: derby2095.p2.diff.txt, oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-2095) Add the ability to populate a
database for the order entry toolkit based upon the TPC-C specification.
Posted by "Sunitha Kambhampati (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunitha Kambhampati reassigned DERBY-2095:
------------------------------------------
Assignee: Sunitha Kambhampati
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-2095) Add the ability to populate a database
for the order entry toolkit based upon the TPC-C specification.
Posted by "Sunitha Kambhampati (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunitha Kambhampati updated DERBY-2095:
---------------------------------------
Affects Version/s: 10.3.0.0
Fix Version/s: 10.3.0.0
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby2095.p2.diff.txt, oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2095) Add the ability to populate a
database for the order entry toolkit based upon the TPC-C specification.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465643 ]
Daniel John Debrunner commented on DERBY-2095:
----------------------------------------------
Also the Populate class contains the same checks as LoadTester. On of the nice things about Junit test fixtures is that it's easy to hook them together. One can see test fixtures as building blocks.
So if Populate needs to run the tests it could just include checks indvidually, like:
suite.addTest(new OETest("testOrdersRows"));
or through some suite like:
suite.addTest(OETest.checkAllRowCounts());
Though I think it would be better to have the checks be in a separate class, e.g. Checks, and have OETest and Populate include fixtures from Checks.
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2095) Add the ability to populate a
database for the order entry toolkit based upon the TPC-C specification.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465645 ]
Daniel John Debrunner commented on DERBY-2095:
----------------------------------------------
It's not so cool that Populate had a CleanDatabaseSetup decorator that cleaned up the database, thus dropping all the insert rows. :-) I removed that from the commit so I could look at the data.
The loaded data does not match the TPC-C spec in one important factor. In the specification identifiers start at 1 (one), e.g. 1-10 for a district identifier, but the patch (and committed) code start with 0 (zero), e.g. 0-9 for district. I know to look out for this because I wasted time once trying to figure out why a TPC-A bechmark was not working at a hardware vendor's site. I discovered the cause was some of the system was using zero-based identifiers and the rest was one-based. :-( In fact double checking the committed code seems to be inconsistent, warehouse and district are 0 based but customer is 1 based, I didn't check the rest.
Committed revision 497297 - Thanks Sunitha
On the load improvements I can't see any need for per-table loading in the short term. I can see a near-term requirement for incremental loads, e.g. load data for an additional N warehouses. That could be some later improvement.
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2095) Add the ability to populate a
database for the order entry toolkit based upon the TPC-C specification.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465632 ]
Daniel John Debrunner commented on DERBY-2095:
----------------------------------------------
I see that you modeled 'LoadTester' on 'OperationsTester' but I think it's overkill. This is because most of the methods in LoadTester are not testing the Load interface, instead they are consistent across any type of load. Thus I think the tests for the row counts can simply be moved into OETest and thus remove the "duplicate" methods that exist now. (OETest.testOrdersRows and LoadTester.testOrdersRows).
I like the Load interface as a concept but I'm trying to understand why the individual table load methods exist on it and the rowsInTable method is there?
Seems like the populateAllTables() is sufficient to load the data, when would the other methods be called through the interface?
I think the SimpleInsert should not have this constructor
public SimpleInsert(Connection conn, short scale) throws SQLException
and instead require callers to use the setupLoad on the interface.
OETest should be testing via the load interface, using setupLoad(Connection, short) rather than the specific constructor.
Assuming the code works (testing now) I'll commit the patch shortly, and the above items can be a later cleanup.
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-2095) Add the ability to populate a database
for the order entry toolkit based upon the TPC-C specification.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel John Debrunner updated DERBY-2095:
-----------------------------------------
Derby Info: (was: [Patch Available])
Patch 2095.p2.diff.txt Committed revision 499116 - Thanks Sunitha
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: derby2095.p2.diff.txt, oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2095) Add the ability to populate a
database for the order entry toolkit based upon the TPC-C specification.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465644 ]
Daniel John Debrunner commented on DERBY-2095:
----------------------------------------------
It's cool that Populate also runs as a pure-Junit test without having to call its main method (as a test anyway since it will default to scale=1).
Looking at the code though, the setUp method will be called for each fixture, thus as it stands many SimpleInsert objects will be created though only one is actually needed. I think with the clean up of the checks that most likely will disappear.
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-2095) Add the ability to populate a database
for the order entry toolkit based upon the TPC-C specification.
Posted by "Sunitha Kambhampati (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunitha Kambhampati updated DERBY-2095:
---------------------------------------
Attachment: oe.load.p1.diff.txt
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Priority: Minor
> Attachments: oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-2095) Add the ability to populate a
database for the order entry toolkit based upon the TPC-C specification.
Posted by "Sunitha Kambhampati (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465636 ]
Sunitha Kambhampati commented on DERBY-2095:
--------------------------------------------
Thanks Dan for your comments. I agree the LoadTester is a overkill. I'll clean it up.
>I like the Load interface as a concept but I'm trying to understand why the individual table load methods exist >on it and the rowsInTable method is there?
>
>Seems like the populateAllTables() is sufficient to load the data, when would the other methods be called through the interface?
Currently for the Order Entry implementation, populateAllTables will be sufficient.
My original intention when adding those methods were thinking if this would be useful for other scenarios/test in the future, thinking more of building blocks concept for tests.. Does that make sense or do you think this may be just overkill.. ?
I'll cleanup the SimpleInsert constructor in a followup patch. Thanks.
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-2095) Add the ability to populate a database
for the order entry toolkit based upon the TPC-C specification.
Posted by "Sunitha Kambhampati (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunitha Kambhampati updated DERBY-2095:
---------------------------------------
Derby Info: [Patch Available]
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: derby2095.p2.diff.txt, oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-2095) Add the ability to populate a database
for the order entry toolkit based upon the TPC-C specification.
Posted by "Sunitha Kambhampati (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunitha Kambhampati closed DERBY-2095.
--------------------------------------
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby2095.p2.diff.txt, oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-2095) Add the ability to populate a
database for the order entry toolkit based upon the TPC-C specification.
Posted by "Sunitha Kambhampati (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunitha Kambhampati resolved DERBY-2095.
----------------------------------------
Resolution: Fixed
Thanks Dan for the commits.
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: derby2095.p2.diff.txt, oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2095) Add the ability to populate a
database for the order entry toolkit based upon the TPC-C specification.
Posted by "Sunitha Kambhampati (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465574 ]
Sunitha Kambhampati commented on DERBY-2095:
--------------------------------------------
I am attaching a patch (oe.load.p1.diff.txt) for review for the load(population) phase for the Order Entry benchmark.
0)Add interface for Load (oe\client\Load.java) so that the load framework is extensible to have different load
implementations.
1)Add the implementation to do the database population using simple insert sql statements per TPC-C specification
Note, this implementation is single threaded. But in future we can add support for multiple worker threads to do the
load phase. (oe\load\SimpleInsert.java)
2) Add cardinality checks for all the tables
3) Add driver that includes performance tests for load phase. (oe\run\Load.java)
4) Add the framework to test the load for a scale of 1 to use it as a functional test. (oe\test\OETest and LoadTester)
5) Remove the earlier skeleton class that loaded only the schema (Load.java is deleted) and instead
Populate.java takes care of providing that functionality.
svn stat:
A java\testing\org\apache\derbyTesting\system\oe\load
A java\testing\org\apache\derbyTesting\system\oe\load\SimpleInsert.java
M java\testing\org\apache\derbyTesting\system\oe\test\OETest.java
A java\testing\org\apache\derbyTesting\system\oe\test\LoadTester.java
D java\testing\org\apache\derbyTesting\system\oe\run\Load.java
A java\testing\org\apache\derbyTesting\system\oe\run\Populate.java
A java\testing\org\apache\derbyTesting\system\oe\util
A java\testing\org\apache\derbyTesting\system\oe\util\OERandom.java
A java\testing\org\apache\derbyTesting\system\oe\client\Load.java
To run the benchmark:
By default, this test will load schema, create constraints before load, and populate database for a scale of 1 and then
perform checks on the tables.
java org.apache.derbyTesting.system.oe.run.Populate
The test takes the following arguments:
/*
* Populate class takes in following arguments currently:
* Usage: java org.apache.derbyTesting.system.oe.run.Populate options
* Options:
* <OL>
* <LI>-scale warehouse scaling factor. Takes a short value. If not specified defaults to 1
* <LI>-createConstraintsBeforeLoad create constraints before initial load of data, takes a boolean value. If not
specified, defaults to true
* <LI>-doChecks check consistency of data, takes a boolean value. If not specified, defaults to true
* <LI>-help prints usage
* </OL>
* To load database with scale of 2, to load constraints after the population,
* and to not do any checks, the command to run the test is as follows:
* <BR>
* java org.apache.derbyTesting.system.oe.run.Populate -scale 2 -doChecks false -createConstraintsBeforeLoad false
* <BR>
*/
I plan to add some consistency checks also in another later patch.
Can someone please take a look at this.
Thanks,
Sunitha.
> Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira