Gary Doades wrote: > > "Starting inserting records" > 31.996000 0.639000 32.635000 ( 35.356000) > 30000 > > For 30000 inserts with all indexes: > > "Starting inserting records" > 32.795000 0.982000 33.777000 ( 37.103000) > 30000 > > I Don't know if it is the hash lookup code or ActiveRecord that is > gobbling up the time, but it certainly isn't the database.
by the way... interesting to find out the CPU time is so much... i thought this code is I/O bound at first... by the way I am using Rails 2.3.2, Ruby 1.8.6 patchlevel 287... on Windows 7. hm... the Hash look up time should be really small... for example, if i just write all data to a text file, it should be really fast... it might be ActiveRecord, although I though ActiveRecord merely translate the method into a SQL statement and so shouldn't be so CPU intensive. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
