[
https://issues.apache.org/jira/browse/DERBY-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-4233:
---------------------------------
Bug behavior facts: [Performance, Regression] (was: [Regression])
> Lower tablescan performance right after database creation in 10.5
> -----------------------------------------------------------------
>
> Key: DERBY-4233
> URL: https://issues.apache.org/jira/browse/DERBY-4233
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.5.1.1
> Environment: Solaris Express Community Edition snv_114 X86
> java version "1.6.0_13"
> Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
> Java HotSpot(TM) Server VM (build 11.3-b02, mixed mode)
> Reporter: Knut Anders Hatlen
> Priority: Minor
>
> I noticed that a table scan test performed significantly worse
> (10-20%) in Derby 10.5.1.1 than in Derby 10.4.2.0. I only see this if
> the test creates and populates a fresh database. To reproduce, put
> derbyTesting.jar from 10.5.1.1 and derby.jar from the release you want
> to test in your classpath, and execute the following shell commands:
> # make sure the database is removed so that we create a fresh one
> test -d db && rm -rf db
> # run test for five minutes (+ one minute warm-up)
> java -server -Dderby.storage.pageCacheSize=25000 \
> org.apache.derbyTesting.perf.clients.Runner \
> -load sr_select -load_opts nonIndexed -wt 60 -rt 300 -init
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
