[PERFORMANCE] Torque vs. Hibernate

[Iwan <ja...@i-ware.net>]

Hi,

Does anybody have any experience, (or results), with performance tests
comparing Torque and Hibernate? We're currently using Hibernate, although I
like Torue better due to the simple format of the schema-definition file. We
have some performance issues with Hibernate and I was wondering if others
have moved from Hibernate to Torque for performance reasons.

Iwan

> -----Original Message-----
> From: Göschl,Siegfried [mailto:Siegfried.Goeschl@drei.com] 
> Sent: Tuesday, December 02, 2003 12:19 PM
> To: torque-user@db.apache.org
> Subject: Torque 3.1 and Prepared Statements ....
> 
> 
> Hi folks,
> 
> I try to convince the company I work for to use Torque 
> instead of the textbook "use entity beans with a session 
> facade plus manually written data transfer object and fill 
> your first dropdown box in two weeks time". To ensure that 
> Torque is doing well I wrote a regression test suite which 
> works fine. The last addition was testing of Prepared 
> Statements which showed a few problems
> 
> +) The current implementation returns a List of 
> VillageRecords. Is there 
> +any reason why not to generate code which does the following 
> conversion 
> +automagically
> 
> Foo.addSelectColumns( criteria );
> ... more criteria wrestling ..
> List recordList = FooPeer.doPSSelect( criteria );
> List result = FooPeer.populateObjects( recordList );
> 
> +) There were question in the mailing list about prepared 
> statements and 
> +a lot of statement parsing within Oracle. I'm not pretty good at 
> +database and my last encounter with ODBC/JDBC is long and happily 
> +forgotten. But looking at the BasePeer.java I think what 
> could be the 
> +reason for that behaviour mentioned above. A conenction is 
> taken from 
> +the pool, a prepared statement is created from this connection, the 
> +query is done and at the end the statement is closed. AFAIK these 
> +forces the database to do the same parsing for the next prepared 
> +statement again.
> 
> Does it make sense to store the prepared statement and all 
> the information needed to create it into a result returned 
> from BasePeer.createPreparedStatement()?! The prepared 
> statement could be reused, if the connection is broken the 
> prepared statement could be recreated using a good connection 
> and most of the parameter handling is already there?! Am I 
> completely on the wrong track?!
> 
> Thanks in advance,
> 
> Siegfried Goeschl
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org

RE: [PERFORMANCE] Torque vs. Hibernate

[Ramesh Sabeti <rs...@reazon.com>]

Iwan,

I don't have an answer, but remember reading a posting about Torque vs.
Hibernate.  Try to do a search on that.  If you find something, please
let us know.  I'd like to see some real world comparison between the
two.

Ramesh.

> -----Original Message-----
> From: Iwan [mailto:java@i-ware.net]
> Sent: Friday, December 05, 2003 9:48 AM
> To: 'Apache Torque Users List'
> Subject: [PERFORMANCE] Torque vs. Hibernate
> 
> Hi,
> 
> Does anybody have any experience, (or results), with performance tests
> comparing Torque and Hibernate? We're currently using Hibernate,
although
> I
> like Torue better due to the simple format of the schema-definition
file.
> We
> have some performance issues with Hibernate and I was wondering if
others
> have moved from Hibernate to Torque for performance reasons.
> 
> Iwan
> 
> > -----Original Message-----
> > From: Göschl,Siegfried [mailto:Siegfried.Goeschl@drei.com]
> > Sent: Tuesday, December 02, 2003 12:19 PM
> > To: torque-user@db.apache.org
> > Subject: Torque 3.1 and Prepared Statements ....
> >
> >
> > Hi folks,
> >
> > I try to convince the company I work for to use Torque
> > instead of the textbook "use entity beans with a session
> > facade plus manually written data transfer object and fill
> > your first dropdown box in two weeks time". To ensure that
> > Torque is doing well I wrote a regression test suite which
> > works fine. The last addition was testing of Prepared
> > Statements which showed a few problems
> >
> > +) The current implementation returns a List of
> > VillageRecords. Is there
> > +any reason why not to generate code which does the following
> > conversion
> > +automagically
> >
> > Foo.addSelectColumns( criteria );
> > ... more criteria wrestling ..
> > List recordList = FooPeer.doPSSelect( criteria );
> > List result = FooPeer.populateObjects( recordList );
> >
> > +) There were question in the mailing list about prepared
> > statements and
> > +a lot of statement parsing within Oracle. I'm not pretty good at
> > +database and my last encounter with ODBC/JDBC is long and happily
> > +forgotten. But looking at the BasePeer.java I think what
> > could be the
> > +reason for that behaviour mentioned above. A conenction is
> > taken from
> > +the pool, a prepared statement is created from this connection, the
> > +query is done and at the end the statement is closed. AFAIK these
> > +forces the database to do the same parsing for the next prepared
> > +statement again.
> >
> > Does it make sense to store the prepared statement and all
> > the information needed to create it into a result returned
> > from BasePeer.createPreparedStatement()?! The prepared
> > statement could be reused, if the connection is broken the
> > prepared statement could be recreated using a good connection
> > and most of the parameter handling is already there?! Am I
> > completely on the wrong track?!
> >
> > Thanks in advance,
> >
> > Siegfried Goeschl
> >
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-user-help@db.apache.org
> >
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-user-help@db.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org