On 16/05/11 10:13 PM, mileszs wrote:
I recently gave a presentation at the Indianapolis Ruby Brigade
monthly meeting, covering aspects of DM I like, and recommending the
crowd give it a shot in their next project. I was asked about
performance, as I knew I would be, but I hadn't really taken a good
run at a performance comparison at the time (which seems like a huge
failure on my part, considering I've put a Rails 3 DM app in to
production). Thus, I sat down yesterday intending to get some numbers
I could show people. Unfortunately, the results were surprisingly
negative for DataMapper. I am hoping that I'm unwittingly performing a
poor benchmark.
As a real world data point, our home page takes upwards of two seconds
to render with datamapper, and ~300ms using SQL wrapped with structs. I
haven't been able to replicate this in a stand alone rails app yet, and
haven't compared to AR. DM object instantiation is pretty expensive.
So YMMV, but in our experience we have found DM to be excellent for our
backend stuff but not ideal for high traffic pages.
(page caching is an option, but I believe it covers up the underlying issue)
[1] theconversation.edu.au, there's a lot of stuff on it
Xavier
--
You received this message because you are subscribed to the Google Groups
"DataMapper" 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/datamapper?hl=en.
