...
Customer can host different types of websites using different technology on one VM which provides ease of administration and provides potential budgetary reliefcost savings.
A summary of the updated features:
...
| Static | CF9 | LAMP2 | Cornell Stack |
|---|---|---|---|---|
Apache | 2.2 | 2.2 | 2.2 | 2.2 |
Coldfusion |
| 9.0.1 |
| 10 |
mod_php |
|
| 5.3 | 5.4 |
php-fpm |
|
|
| 5.4 |
Python |
|
| 2.7 | 2.7 |
Ruby |
|
| 1.8.7 | 1.9.3 |
| Anchor | ||||
|---|---|---|---|---|
|
In CF9/LAMP2 each "instance" represented a separate apache instance that could be started/stopped independently. This provides a high level of isolation, but can also consume more system resources and complicate server administration. The "shared" apache instance makes it possible to host a larger number of instances on a single apache instance while still providing isolation between the instances.
| Standalone | Shared |
|---|---|---|
Apache | 2.2 | 2.2 |
Start/Stop Apache | Yes | Yes* |
mod_cgi | Yes | No |
Custom virtualhost include | Yes | Yes |
mod_php | Yes | No |
PHP-FPM | Yes | Yes |
Start/Stop PHP-FPM | Yes | Yes |
Coldfusion | Yes | Yes |
Start/Stop Coldfusion | Yes | Yes |
Python | Yes | Yes |
Ruby | Yes | Yes |
*Will start/stop ALL sites that are behind the shared Apache
How many instances
Using a VM with 2 GB of memory the following are some guidelines on possible deployments. Individual applications may vary (i.e. it's possible to have a single PHP/Python/Ruby/Perl application that consumes 100% of the memory. Increasing the amount of memory may make it possible to run more instances, but it is not a recommended best practice.
...