[DERBY-4233] Lower tablescan performance right after database creation in 10.5

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Invalid
• Affects Version/s: 10.5.1.1
• Component/s: SQL
• 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)
• Bug behavior facts: Performance, Regression
• Assignee: Unassigned
• Reporter: Knut Anders Hatlen
• Created: 18/May/09 10:32
• Updated: 13/May/11 06:53
• Resolved: 31/May/09 03:26

Description

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:

1. make sure the database is removed so that we create a fresh one
   test -d db && rm -rf db
2. 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

Issue Links

• is related to: DERBY-5206 Investigate reduced throughput in some of the nightly performance tests
• relates to: DERBY-3678 StackOverflowException in deadlock trace