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] Commented: (DERBY-4233) Lower tablescan performance right after database creation in 10.5
Date Mon, 18 May 2009 10:35:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710327#action_12710327
] 

Knut Anders Hatlen commented on DERBY-4233:
-------------------------------------------

After a binary search I pinpointed it to this commit:

------------------------------------------------------------------------
r666901 | dag | 2008-06-12 01:41:43 +0200 (Thu, 12 Jun 2008) | 4 lines

DERBY-3678 StackOverflowException in deadlock trace

Patch derby-3678-3 which solves the issue and adds a new regression test.

------------------------------------------------------------------------

The only engine code touched by that commit was in impl.sql.catalog,
which is consistent with the observation that the problem is only
manifested if a fresh database is created.

> 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: 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
>
> 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.


Mime
View raw message