db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian McCallister <bri...@apache.org>
Subject Re: Derby not as fast as hsqldb ?
Date Mon, 02 Jan 2006 19:29:51 GMT
HSQLDB doesn't do things like transaction isolation or guaranteed  
consistency on a crash/restart. This might affect it.

-Brian

On Dec 31, 2005, at 9:15 PM, ivan ooi wrote:

> Hi all,
>
>   I did an insert 5096 rows test on Derby and HSQLDB. i found out
> HSQLDB a bit faster... Anythings else that i miss in this test ?
>
> Here is the test :-
>
> Derby
> ---------
> org.apache.derby.jdbc.EmbeddedDriver
> url=jdbc:derby:DerbyTest;create=true
>
> Auto Commit off.
>
> using global temporary table.
> (cached table was used in HSQLDB)
>
> Created a table with 18 columns. ( A real situation)
> Column type included INTEGER, VARCHAR, TIMESTAP and NUMERIC
>
> Derby database page size set using :-
> CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY 
> ( 'derby.storage.pageSize','32768')
>
> Prepared statement was used.
>
> execute using Batch process.
>
> Derby      result : 3395ms
> HSQLDB result : 1011ms


Mime
View raw message