I just had a very unpleasant experience of having a big traffic spike on my site. It's running on a vps. We added a total of 10 cores, and the cpu was still pegged. Host had the bright idea of going to 10 worder processes, and wow, what a difference that made.
What are the issues with running in a garden? We only use Umbraco like a blog/news site. There's no users other than admin for accessing the backend. There's no other interactivity. Is there any way to run this as a garden successfully?
Yes, I knew it had been discussed. I was wondering if there was anything new. Since the site typically does not have much of a load, I'm considering just moving to multiple worker processes during times of heavy load (and not updating the site), then going back to one process when we either need to update, or when the storm has passed. I'm looking into cdn's that claim to serve dynamic content to see if this is a cost effective solution. The site is typically updated once or twice a day, so caching is very practical. Load balancing doesn't seem like a good solution for a site that typically doesn't need that type of capacity. But any suggestions would be really appreciated!
7.1.8 In a web garden?
I just had a very unpleasant experience of having a big traffic spike on my site. It's running on a vps. We added a total of 10 cores, and the cpu was still pegged. Host had the bright idea of going to 10 worder processes, and wow, what a difference that made.
What are the issues with running in a garden? We only use Umbraco like a blog/news site. There's no users other than admin for accessing the backend. There's no other interactivity. Is there any way to run this as a garden successfully?
Thanks!!
Stephanie
Hi Stephanie,
I'm not sure myself but it has been discussed before here. You could also consider load balancing for which there is documentation here.
Jeavon
Yes, I knew it had been discussed. I was wondering if there was anything new. Since the site typically does not have much of a load, I'm considering just moving to multiple worker processes during times of heavy load (and not updating the site), then going back to one process when we either need to update, or when the storm has passed. I'm looking into cdn's that claim to serve dynamic content to see if this is a cost effective solution. The site is typically updated once or twice a day, so caching is very practical. Load balancing doesn't seem like a good solution for a site that typically doesn't need that type of capacity. But any suggestions would be really appreciated!
Thanks!
Stephanie
is working on a reply...