We've recently upgraded our fortrabbit.com website, including a complete overhaul of our pricing visualization. The visualization is one thing, the other is our Map your App decision-helper: One of the major problems all hosting providers have to solve (or should at least try) is to make it transparent to the customer what kind of resources she needs.
Tell us your life story, please
Well, the major problem is that no two web applications are the same. Even if they are based on the same technology stack, say framework XYZ, their actual resource requirements can differ widely. So, to tell you what resources you need, from a hosting provider perspective, requires a deep understanding of the inner workings of your App. Just to name a few:
- What PHP technology stack it's build on? Eg framework X or CMS Y;
- What other technologies are employed? Eg database, image transformation, PDF generation;
- How are those technologies used? Eg PDF generation for once-a-month reporting vs on-demand, possibly every minute or even second;
- How does the resource usage scale with more visits/requests? Eg each request thumbnails an image vs once a day;
- How do visits translate to (PHP) requests? Eg an REST API where every "visit" is a request vs a media-heavy CMS in which each visit creates multiple requests;
- Is caching used, to what degree (eg about everything vs "this one expensive query") and by what measure (eg file vs memcache vs database vs ..) This is of course not all (far from it), but you probably get the point: It's about impossible for us to tell you what resources your App will need when we don't know what you are actually doing. And we need to know this quite detailed and of course in the foreseeable (and beyond) future.
Is all that really necessary to know? We'll, actually it isn't. What it boils down to are two factors:
- How long does your App need on average to render (milliseconds)?
- How many visitors do you have? Ok, there are two more: how expensive is it in terms of CPU? However, this is only a (relevant) factor if you do stuff like image transformation or so. However, if this really is an often performed operation, it should not be done in the web part of your application anyways (that's what workers or third party image transformation APIs and so on are for). Then there is how much memory does your application require, especially in terms of APC usage, as we offer different sizes with our plans.
First step is to take the amount of visitors, applying a simplified standard distribution over the day and determine the peak amount of total requests per hour. With the average render time per request, you can now get to the estimated amount of required parallel running processes. And that's about it.
As the whole estimation is - well - an estimation and the purpose is to give you a reasonable prognosis on what you will need, we can factor in our experience. So we defined three "sizes" and named them slim, average and fat. Each size implies an average render time and is expressed through examples of underlying PHP technologies, to which you can relate. From our experience, the used PHP technology and the actual render time are strongishly related. (Yes, it's not impossible to build an App using Slim Framework which renders in minutes, not milliseconds, but it simply does not happen all that often) Finally, what we need to know is how many visitors do you expect and can give you a reasonable realistic estimation what resources you'll need. The only thing we need to know additionally are "special requirements", such as whether you want to use SSL or not (can't simply not be deduced from the above).
As you might have noticed, I somewhat overused the word estimation here. The thing is: the at the beginning stated concerns are valid non-the-less. As a hosting provider, we can only speak in averages and a specific App could easily deviate from those averages. Let me put it this way: the bigger the deviation, the smaller the probability. A Symfony App, which we consider average-size, could surely render slower and need more resources in every aspect than an normal sized Mangento shop, which we consider fat. Still, it's just not very likely to happen often.
You are up
So, to help us make our estimations become true, we recommend to get familiar with our App design and optimization guide. Good application of caching can make a fat App render like an average or even slim - at least where it matters: on the visitor side. Leveraging web storages, such as S3, can reduce I/O for media-heavy Apps vastly and reserve your App's fortrabbit resources for PHP processing. And that's just the tip of the iceberg. In the end, we are in this together.