db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-110) hsqldb is faster than derby doing inserts
Date Mon, 29 Jun 2009 14:47:47 GMT

     [ https://issues.apache.org/jira/browse/DERBY-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dag H. Wanvik updated DERBY-110:
--------------------------------

    Derby Categories: [Performance]

> hsqldb is faster than derby doing inserts
> -----------------------------------------
>
>                 Key: DERBY-110
>                 URL: https://issues.apache.org/jira/browse/DERBY-110
>             Project: Derby
>          Issue Type: Test
>    Affects Versions: 10.0.2.1
>         Environment: CPU 2.40GHz
> windows 2000
>            Reporter: Zhang Jinsheng
>            Priority: Minor
>
> 1. create db name systable in derby and hsqldb (another open source dbms);
> 2. create table named a table ('CREATE TABLE aTable(id INTEGER NOT NULL, name VARCHAR(255)
NOT NULL, description VARCHAR(255))');
> 3. insert ten thousands row in table "atable"
>     for(int i=1; i<10000; i++) {
> 	sql = "INSERT INTO aTable VALUES("+i+", 'haha', 'zhang'' test')";
> 	stmt.execute(sql);
> 	System.out.println(i);
>     }
> 4. derby spend 50390 millisecond;
>    hsqldb spend 4250 millisecond;
>  
> 5. conclusion: hsqldb has more perfect performance.
>    Maybe derby need to improve it's performance.

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