[
https://issues.apache.org/jira/browse/DERBY-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olav Sandstaa updated DERBY-2657:
---------------------------------
Attachment: TestClient2.java
Test client that can be used to show that there has been a performance
regression.
This test is based on a slightly modified version of the test client found in
DERBY-1961. The main change is to add a secondary index to
it that is used for the queries.
To run this client do:
1. Create and initialize database:
java TestClient2 -a initdb -u "jdbc:derby:/tmp/tulldb;create=true"
2. Run test (which does SELECT * FROM ... WHERE SEC_ID= X) with two
client threads:
java TestClient2 -a select -r 60 -c 2 -u "jdbc:derby:/tmp/tulldb"
> Performance regression after check-in of svn 531971
> ---------------------------------------------------
>
> Key: DERBY-2657
> URL: https://issues.apache.org/jira/browse/DERBY-2657
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.3.0.0
> Environment: Solaris/Linux, Sun JDK 5 & 6, IBM 1.5
> Reporter: Olav Sandstaa
> Attachments: TestClient2.java
>
>
> After check-in of svn 531971 on DERBY-2537 it seems like there for
> some loads are a performance regression of about 10-15 percent.
> For more info about this issue see the following mail thread:
> http://www.nabble.com/Performance-regression-after-check-in-on-DERBY-2537-(SVN-531971)-t3651494.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
