Comments on: 10 tips to boost up performance of your ruby on rails application

By: Abdul Barek

Abdul Barek — Fri, 24 Feb 2012 17:13:44 +0000

Good Post Fuad vai!
I am adding a little stuff.
“Load content whenever the content is being appeared on the monitor – this will reduce page loading time”. JQuery appear plugin can be a good friend :)

By: nhm tanveer hossain khan

nhm tanveer hossain khan — Wed, 23 Nov 2011 03:19:53 +0000

Regarding #6. Avoid dynamism

i think on production environment where class caching is turned on, this shouldn’t be a performance issue. because those are dynamically pre defined or on first time call they generate them.

Regarding #4

Is there any reason why you have chosen if – then – else over ruby ternary operator ?
condition ? if-true : if-false

btw thanks for the nice post.

By: Kowser

Kowser — Fri, 29 Jul 2011 16:58:26 +0000

I think I am still learning… ;)

Yes glad to know the practices which should be followed the topics you mentioned.

Just to give my feedback
“…good practice are indedependent of any language”, exactly.

That is why I expected, this topic title or something could be changed. The reason I am saying is, when I recommended it to someone, the feedback was like, “… oh, its ruby, I am not sure how much it could be helpful for me.”. I believe you can understand me.

This topic has more value than ruby. And at least me want know more things like these ;)

By: Fuad

Fuad — Fri, 29 Jul 2011 07:11:06 +0000

Kowser, well ruby is natural, don’t you get the code? If the player’s name is Tamim it will return player object otherwise a nil :-)
Well, It is focused to rails, but good practice are indedependent of any language, don’t forget to share with us once you go deeper.

By: Kowser

Kowser — Fri, 29 Jul 2011 06:16:18 +0000

I am not a ruby guy, but wondering how it works, the syntax u suggested for DRY. I am a bit lazy to google for it.

player = Player.find_by_id(1)
if(player.name == “Tamim”) then player else nil end

And I believe most of the suggestion works for languages rather than ROR. It should suffice for any webapp whether it is in Java/PHP/… or any other languages.

To me its a starting point to think about these optimization.

By: Tanvir Anowar

Tanvir Anowar — Fri, 29 Jul 2011 05:16:27 +0000

Hello Fuad vi
Very nice article. Hope it will increase our software engineering practice.But I have faced some performance issues regarding eager loading. From the developer side its something like heavenly gift but from the client’s side it rises execution time issues sometime ( depending on tables and data volume ), specially when you are dealing with AJAX call (when the AJAX loading image remains popped-up and seams like the app has gone in hang state).

Thanks for this helpful article.