Chris,
I have used Castor for basic OR/Mapping and straight JDBC when performance
is a factor. Speaking from a general perspective rather than from Castor
benchmarks, one generally chooses OR Mapping tools such as Castor JDO when
you want to save time and redundant JDBC code. If you need to achieve large
performance gains when doing complex joins or bulk inserts, you may wish to
use JDBC batch updates or optimized queries. I have done this on numerous
J2EE projects using a combination of the Data Access pattern, Castor JDO,
and JDBC 2.0.
In short, use Castor to save time on the common CRUD (create, read, update,
delete) and use straight JDBC for performance gains on bulk inserts using
batch updates and manually tuned SQL.
Hope this helps,
James
----- Original Message -----
From: "Chris Cook" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 27, 2001 10:42 AM
Subject: [castor-dev] Performance
>
>
> I have recently downloaded and started to use Castor for a project. We
had
> in place a set of code to simulate a piece of our system, and measure the
> inserts per second into the database. Using straight JDBC we usually
> measure about 175 ins/s into the database. With Castor doing the
> persistence, we measure about 40 ins/s. Does this figure seem right to
you
> all? Does Castor average about 4 or 5 times slower than straight JDBC?
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
>
>
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
