Thursday, December 11, 2014
While some of the advice here is good, it represents a very confused view of performance optimization. For instance, #2 is just plain bad advice for performance (but good for modularity) - partial rendering has a ton of overhead in Rails. #3 doesn't speak to performance at all. DRY (#4) is not a performance principle. I stopped when the author repeated #4.
On Wednesday, December 10, 2014 3:51:02 PM UTC-5, Colin Law wrote:
-- On Wednesday, December 10, 2014 3:51:02 PM UTC-5, Colin Law wrote:
On 10 December 2014 at 17:43, Dante Elrik <li...@ruby-forum.com> wrote:
> Mehreen wrote in post #1163991:
>> Hello guys!
>>
>> I found a guideline which will help to boost up performance of your Ruby
>> on
>> Rails application
>>
> <http://www.nascenia.com/10-tips-to-boost-up-performance- >.of-your-ruby-on-rails- application/
>> You should check this out.
>
> I'd like to! Link is dead.
It works for me. Some of the suggestions are way out of date though,
being written in 2011!
Colin
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/5261a95e-ff88-42f2-a020-f443932d1a9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment