558 Posts in 3573 Topics by 244 members
|Go to End|
14 June 2013 at 2:23pm Last edited: 15 June 2013 11:00am
Is it possible to run three SS sites on one shared host account? The account has 64 mb ram?
Is it possible to run three SS sites on one server? The server has 64 mb ram?
14 June 2013 at 4:17pm
There should be no problem at all running multiple SS3 installations on a single virtual server with 2GB RAM. Our pre-production server has a couple of dozen sites on separate vhosts and we don't have memory problems.
However... 64MB sounds tiny. Like 1980's tiny. Did you mean 64GB?
14 June 2013 at 5:01pm Last edited: 14 June 2013 5:01pm
Sorry I should have said the three sites are running in a shared hosting environment under one account. Our account has 64mb of memory assigned to it.
The three sites are using separate SS installations. Each SS instance has been installed in a sub-directory off the main plugin_html directory. Like
The three sites are accessed with three separate domains.
Lately I've seen a couple errors like:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 80 bytes) in /public_html/mysite/SomePage.php on line XXXX
SS requires 48mb of memory. Silver Stripe Server Requirements.
Does that mean our account needs 144mb (48 * 3) or should 64mb be sufficient?
Tapio (Flo Apps)
15 June 2013 at 1:44am
As SparkGreen said, 64mb is very little. Usually something like 1-2 GB RAM (at least) is needed for the server to run smoothly.
That 48MB (in SS requirements) is the maximum allowed for a single process. That means, if you have just 2 simultaneous users doing memory-intense processes, they'll eat up 96MB of resources and your server will start suffering from those memory problems.
(Not an expert on this, maybe someone else can elaborate on this.)
15 June 2013 at 10:41am
The webhosting side of things is pretty new to me as well.
1 August 2013 at 6:21pm Last edited: 1 August 2013 6:22pm
SilverStripe out of the box will use around 48MB memory per-process, but when you start adding custom code and doing more complex tasks it will use more than that.
Note that processes are not per-user, they're used to serve multiple users and requests. Apache usually has a limit depending on the amount of RAM the server has, so if it has around 1GB RAM, and if PHP has a memory limit of 64MB per process, then Apache will have a maximum of around 16 processes (1024/64) (but usually a bit less than this, because the OS has overhead on the available RAM, and also shared hosts have probably got a far more conservative number than a dedicated or virtual machine.)
64MB in this case is the probably the maximum your host is allowing per-PHP process. This isn't a whole lot, and bigger sites will use something more like 128MB per-process.
1 August 2013 at 7:30pm
Thanks for the clear response Sean.
2 August 2013 at 9:56am Last edited: 2 August 2013 9:56am
One thing to try is adding this to the top of your mysite/_config.php in each site:
It depends on whether the host has locked this down or not, though.
|Go to Top|