db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4233) Lower tablescan performance right after database creation in 10.5
Date Mon, 18 May 2009 10:33:45 GMT
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: Performance, SQL
    Affects Versions:
         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

I noticed that a table scan test performed significantly worse
(10-20%) in Derby than in Derby I only see this if
the test creates and populates a fresh database. To reproduce, put
derbyTesting.jar from 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.

View raw message