Deployment Sizing and Capacity Planning

Internal and external deployments require different hardware configurations because internal sites generate more database activity compared to the number of page views.

Internal Deployments

For internal deployments, expect a higher ratio of actions that write to the database. This includes creating new content, adding comments and replies, updating content, and so on. Here, writes are estimated as 15 percent of the number of page views.

Page Views per Month Database Writes per Month CPUs (at least 2 GHz) RAM Location of App Server, Activity Engine, and Database(s) Clustered?
500,000 75,000 1 dual core CPU 3 GB, 2 GB Java heap Separate boxes No
1,000,000 150,000 1 dual core CPU 3 GB, 2 GB Java heap Separate boxes No
5,000,000 750,000 1 dual core CPU 4 GB, 2 GB Java heap Separate boxes Yes
10,000,000 1,500,000 1 dual core CPUs 4 GB, 2 GB Java heap Separate boxes Yes
25,000,000 3,750,000 2 dual core CPUs 4 GB, 2 GB Java heap Separate boxes. Database box is a quad core. Yes

External Deployments

In general, an external deployment is going to have a very high ratio of page views relative to database writes. That's because external deployments tend to support communities with a large number of people who rarely contribute but often check back to read what others are posting.

Page Views per Month Content Created per Month CPUs (at least 2 GHz) RAM Location of App Server, Activity Engine, and Database(s) Clustered?
500,000 20,000 1 dual core CPU 3 GB, 2 GB Java heap Separate boxes No
1,000,000 20,000 1 dual core CPU 3 GB, 2 GB Java heap Separate boxes No
5,000,000 50,000 1 dual core CPU 4 GB, 2 GB Java heap Separate boxes Yes
10,000,000 50,000 1 dual core CPUs 4 GB, 2 GB Java heap Separate boxes Yes
25,000,000 100,000 2 dual core CPUs 4 GB, 2 GB Java heap Separate boxes/DB box is a quad core Yes