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-4227) performance degradation of with simple queries & no data retrieval
Date Wed, 13 May 2009 09:20:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708844#action_12708844

Knut Anders Hatlen commented on DERBY-4227:

I printed some more timestamps and found that of the ~80 ms reported by the test, ~30 ms was
spent compiling the statement. To get a better picture of the performance of executing the
statement, it's probably a good idea to put PreparedStatement.executeQuery()+ResultSet.next()
in a loop and execute it, say, 10000 times.

> performance degradation of with simple queries & no data retrieval
> ---------------------------------------------------------------------------
>                 Key: DERBY-4227
>                 URL: https://issues.apache.org/jira/browse/DERBY-4227
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions:,
>            Reporter: Myrna van Lunteren
>         Attachments: scanperf.java
> I have been executing some non-contributed (and not easily contributable) performance
tests, and found that across the board, with the exception of some blob streaming and complicated
queries, performs significantly worse from
> I've turned one of these tests into a little repro script.
> It's decidedly hokey, but if you execute this repeatedly (removing the wombatC db and
derby.log each time) you'll likely find the same. I executed this on an MS-Windows 2000 machine,
with ibm 1.5. jvm.
> As a quick comparison, I got the following data out of executing the repro 4 times with
a fairly recent build (706492),, and Time is the elapsed time
printed out at the  end by the repro.
> version
> 1st run      187               219             328
> 2nd run     172               172             328
> 3rd run       203              234             313
> 4th run       187               281            344
> We should identify why a simple select without actually fetching the data would do so
much worse with

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message