You probably have done this, but does your Raw SQL statement match the one generated by Torque exactly? Sometime statement syntax differences can generate different execution plans which causes one query to use indices and another not to.
In my experience this is the most likely suspect for Select performance problems and generally can be fixed by adding appropriate indices. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > On 14/06/06, Tassos Bassoukos <[EMAIL PROTECTED]> wrote: > > > > On 6/14/06, Joe Carter <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > Thanks for the info. > > > I've tried it and it makes no obvious difference to the speed. > > > > > > FWIW my timings for selects (for my particular test) Standard > > > Torque: ~10 seconds Raw SQL: ~4 seconds SQL as Prepared > Statement: ~ > > > 3 seconds. > > > Duke CE Privacy Statement Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
