Hard resource limits and the upcoming hard disk quota enforcement are always applied per website. Therefore the maximum usage on a package is numberOfWebsites x resourceLimit. For example, if you have a plan with a memory limit of 4GB and 5 websites then the maximum memory that customer can consume is 20GB.
Of course "addon domains" created under a single website will run within the same container/namespace and will therefore be limited in aggregate to the per-website resource limits of the package.
There is additional functionality we can add in the future. For example the ability to set an overall resource limit on a package and have the customer sub divide the available resources between their websites. We didn't implement that for v1 because we felt it might be confusing for end users. Also, for customers on dedicated packages, we can provide the ability to see and set the per-website overrides.
If customers want it, it is technically possible to provide hard system resource limits across the entire plan. The downsides of this are that:
- All of the customer's websites would be disrupted when this limit is reached
- All of the customer's websites would need to be placed on the same server