In one of our apps, common objects (that cause a number of cascades)
takes about 1s to .make (there's a lot of callbacks and whatnot going on
here also). Objects close to the bottom of the tree take 0.1s to create.
In a new app, each object creation is adding about 0.02s (sounds tiny
buts add up quick).
As a percentage these numbers are far bigger than most other operations
in our suite (we do have some app tasks that take a while, but we know
where those are).
On 17/03/10 2:29 PM, Pete Yandell wrote:
On 16 March 2010 17:54, Xavier Shay<xavier-l...@rhnh.net> wrote:
- Either some sort of profiling, where machinist records object creation and
builds up a library (so first run will be just like normal, second run will
be optimized)
Now that would be cool! But I have a question first:
Has anyone done any profiling on their Rails app tests to work out
where the time goes? I've always wondered how much of the time testing
Rails apps is wasted on the database syncing disk writes, etc. If you
threw your test database on a ramdisk, how much performance would you
gain?
- Pete
--
You received this message because you are subscribed to the Google Groups "Ruby or
Rails Oceania" group.
To post to this group, send email to rails-ocea...@googlegroups.com.
To unsubscribe from this group, send email to
rails-oceania+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rails-oceania?hl=en.
