Wednesday, July 23, 2014
On Tuesday, 22 July 2014 23:44:12 UTC-4, Ruby-Forum.com User wrote:
Hi everyone,
My name is Michael Solovyov and I'm the co-founder & CTO of a
rails-based start-up. We have built a product for other businesses to
help their users adopt their products.
We've built the application, delivered to a few customers and now we've
hit scaling and performance issues.
I'd love your feedback on how we proceed as we try to resolve them:
http://stackoverflow.com/questions/24901078/scaling- optimizing-a-slow-ruby-on- rails-application
Some thoughts:
* as mentioned on SO, New Relic is a good place to start. Figure out where the time is going in the slow requests, and work from there.
* the rewrite to an RDBMS may help, may not. It's highly dependent on why CouchDB was chosen in the first place - if your application depends heavily on some of the features of CouchDB (MapReduce, or async replication) it may make things worse.
* if minor parts are hard to port from Couch, skip them. Get something working with the new design, and benchmark it.
* Above everything else, MEASURE. Most of the things you listed on StackOverflow *could* improve performance, but *could* decrease it.
--Matt Jones
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/264641b8-7c48-428f-be15-38f6925e244e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment