Hosting and the Woes
Posted by Annalisa Afeltra in
Ruby on Rails -
no comments
Ezra Zygmuntowicz, Jamie van Dyke e Tom Mornini talk about the difficulty intersected in hosting a rails application
I am sitting at a round table amongst the participants are part of Engineyard, the live motif of the session and clear hosting, how to create a good system for hosting RoR?
The session will include a few problems that are linked to the world of hosting Rails;
ActiveRecods
ActiveRecord is fantastic in terms of functionality, but a a pest in presentation, to this it is added that in the major part of the cases it is forgotten to utilize the indexing of the database. Other than the indexing specifying in order the wrong useless results during the joins. (a good strategy to remedy the problem and use the statement SQL EXPLAIN)
Sphinx is a good solution to reduce the index dimension, much better performance than Ferret.
Image Science
EngineYard uses Monit to monitor the service but this becomes a problem with the various environments, but they say that the problem has been easily resolved.
Hodel 3000
This product modifies the format of logs of Rails, its only problem is that, if you do not change the settings in the configuration file, it generates a lot information on the debug.
How to manage the traffic peaks?
What happens if your website uploads in the homepage of Digg? The solution is to cache each page possible, but not always can you apply this solution (for example the signup procedure), in this case it is important to benefit the caching of queries.
When do you influence the choice of the server?
Between ebb, mongrel and thin there is not much of a difference, the quality of the product code counts more and the caching the procedure implemented.
Annalisa
