db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank-Ralph Reiser (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2634) CLOB performance partially very poor on linux system
Date Fri, 11 May 2007 09:15:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495005
] 

Frank-Ralph Reiser commented on DERBY-2634:
-------------------------------------------

My mistake: In the example, the simple selects are wrong: The resultset is empty in those
cases (where ID='1-1' would be correct!).

The select statement and it's complexity doesn't change the duration of ResultSet.next().


> CLOB performance partially very poor on linux system
> ----------------------------------------------------
>
>                 Key: DERBY-2634
>                 URL: https://issues.apache.org/jira/browse/DERBY-2634
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Client, Network Server, Performance
>    Affects Versions: 10.2.2.0, 10.3.0.0
>         Environment: gnu linux, network client and network server on the same machine
>            Reporter: Frank-Ralph Reiser
>         Attachments: derbytest-linux-laptop-1.66GHz.txt, testcase.zip
>
>
> Doing some performance tests with several differente database implementations, we noticed
very poor query performance of apache derby under certain conditions.
> If the select statement selects a CLOB column and if it contains a subselect, traversing
the ResultSet takes very long with nearly no cpu load.

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