david
david

Hello everyone!

I had a question about how October scales, and what is considered the best practice for the following setup:

A current production stack that we use with out CMS software looks like the following:

Load Balancer (HA Proxy) -> Application Servers (nginx/varnish) [auto scaling] -> Central MySQL server with read replica

My questions are:

  • Does October handle sessions across multiple applications servers effectively?
  • Does October mind being ran on 2 - 100 applications servers/ are there any known scaling issues with this?
  • Does October play well with Varnish?
  • What all is the Central MySQL server used for?

Generally we disallow any changes on production, changes must be forced through a staging server then pushed by automation tools.

Thanks for any info!

dgallardo14583
dgallardo14583

Hi everyone,

Im interested in this topic also. We are building a complex website (migrating from an existing website) with some high traffic between 5.000 to 10.000 visits per day.

I would like to setup the APP:

  • 1 Load Balancer
  • 3 Application Servers
  • Media Content on S3
  • Mysql with 1 Master and 2 Slaves
  • Cache with Memcached and Varnish

Questions:

  • Which is the recomendation for high traffic web sites, I know this site is running on October CMS, how is the current setup ?
  • Does October play well with Varnish ?
  • Does Varnish have some setup of Master / Slave configurations ?
jazerb17941
jazerb17941

No responses to this? Were you guys able to land on a solution? @david mentioned disallowing edits on production which is a good idea (editing content blocks, etc.). However, what if you wanted to allow certain content to be edited. How does that replicate across the cluster?

manrox.drag17392
manrox.drag17392

even i want to know how to go ahead and do this

manrox.drag17392
manrox.drag17392

dgallardo14583 said:

Hi everyone,

Im interested in this topic also. We are building a complex website (migrating from an existing website) with some high traffic between 5.000 to 10.000 visits per day.

I would like to setup the APP:

  • 1 Load Balancer
  • 3 Application Servers
  • Media Content on S3
  • Mysql with 1 Master and 2 Slaves
  • Cache with Memcached and Varnish

Questions:

  • Which is the recomendation for high traffic web sites, I know this site is running on October CMS, how is the current setup ?
  • Does October play well with Varnish ?
  • Does Varnish have some setup of Master / Slave configurations ?

did you find a way for this ?

patos
patos

+1. A tutorial for that would be great.

candrabeqx
candrabeqx

Such a great topic but left without any good solutions.

I think I'm gonna share what I've done so far... I setup OCMS to run on a 6-server running with editable content (admin able to add/edit content, pages, etc... basically do anything on the backend).

To make sure everything works smoothly, I use memcached as the default caching provider, and the backend is not load-balanced (this is done via nginx) to make sure everything being updated to only 1 server. Then I copy all the changes to other servers using rsync, set up with cron (run every minute). User will still find some delays, but it will not a major issue.

w3labz
w3labz

Hi, I was faced with same issue of scaling up a Portal. Initial Load of users was not known and when it goes live from initial 1000 users per day it went upto 10000 users per day.

My Initial Configuration was 2GB RAM/2 Cores/80 Gb HDD. With this config 3000 users per day was not a problem with apache+nginx+varnish but as the load increased to >5000 users per day we were facing CPU and RAM chocking issue. So, We doubled the resources and it was able to manage the load.

This portal is on a VPS.

1-8 of 8