Hosting Considerations for High Traffic Application

Question

I have a question about hosting for a high traffic application. The fact is that I have 3/4 years of experience working with Ruby on Rails applications, but I have never had a website with high traffic. I am very happy because it is the "next level" for me and my colleague. The fact is that we have no experience using the rails application to handle "high traffic", first of all let me define "high traffic" in this case.

We are developing a rail application for one of the leading providers of Dutch telecommunications services and approx. There will be about 400,000 visitors per day. We program in Ruby 1.9.2 and Rails 3.1. We use the device for authentication. But we are looking for a reliable side to host this application. We look at Heroku, but I do not know what I need, and how many workers, dynos and / or dedicated databases I need. We need to stream movies, and we plan to put them on an amazon s3 bucket.

So, I am looking for advice regarding Heroku and / or other professional and reliable parties. Is there anything I need to take into account regarding the use of rails?

Thank!

Answer 1

This is pretty easy to work out roughly in terms of dynos.

The dyne is single-threaded, so if your page takes 200 ms to render, you can display 5 pages per second. You need to find out how many pages per second 400,000 users will do. Then you know how many pages per second are being requested and what one dyno can handle. Thus, you simply increase the number of speakers until you meet your user requests per second.

e.g. 1 dyno @ 200ms = 5 pages per second 2 dynos @ 200ms = 10 pages per second

.. , , .., , Heroku , , , put.

, , .., , , .

20Gb, , , , , 200 .

- ? ,