[ http://nagoya.apache.org/jira/browse/DERBY-110?page=comments#action_57034 ] Gerald Khin commented on DERBY-110: -----------------------------------
Did you create an In-Memory table (default in hsqldb) when using hsqldb or cached tables? Did you turn autocommit off when using derby? > performance > ----------- > > Key: DERBY-110 > URL: http://nagoya.apache.org/jira/browse/DERBY-110 > Project: Derby > Type: Test > 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. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
