On May 18, 12:58 am, "Mislav Marohnić" <[EMAIL PROTECTED]> wrote: > It would be good to know what is this treshold.
For some reason I'm unable to reproduce that problem now. Perhaps I was mistaken. > It is possible that there is a performance boost on raw queries, but that > it's not visible because the ActiveRecord object instantiation time is an > order of magnitude higher. > > Also, simple queries against a database that has a miniscule amount of > records don't benefit much from having a cached execution plan. You could > first benchmark several hundred thousand INSERTs, then UPDATE those records, > then query those tables with SELECTs with as much conditions and joins you > could throw in. Don't forget the database indexes which play an important > role in laying out the execution plan. I've searched Google for benchmarks on prepared-vs-unprepared statements, and to my surprise I couldn't find any. I'll try to setup a good benchmark. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
