4 ms·
Yes, you can do 200 r/s on a site that doesn't do much. If you are doing something like https://www.tanga.com/deals/watches https://www.tanga.com/deals/watches
by joevandyk 13y ago
Yes, you can do 200 r/s on a site that doesn't do much.
If you are doing something like https://www.tanga.com/deals/watches https://www.tanga.com/deals/watches where what's shown changes completely depending on who's looking at it, you will not get that sort of performance.
Unless you cache the heck of out everything, but that just works around Ruby being slow at generating HTML and Rails being slow at rendering partials, creating URLs, etc.
- fleitz 13y agoSlurping in a whole tonne of data from SQL and sorting it on the app side is going to be slow anyway. Better off leveraging SQL, or pre-computing the result sets in SQL.
- joevandyk 13y agoRails being slow to render templates/html/urls/etc has nothing to do with SQL. Again, this likely only happens with larger code bases, lots of routes, views, controllers, etc.