Hi Egor, While we don't know exactly what you will be running within those Farms, so can't say definitively, given the number of Farms/Servers you plan to run, the configuration that you describe seems sufficient.
Having a second MySQL (slave) instance for replication is of course always a good idea if you desire. Thanks, Michael On Tue, Jan 12, 2016 at 11:44 AM, Egor blajenov <[email protected]> wrote: > Hello. > I'm going to upgrade my Scalr Deployment from 5.1.0 to latest version. > Currently, we using 2-server Deployment, with the following configuration: > > t2.medium RDS instance for MySQL - (2 Cores, 4G Ram) > m3.large EC2 instance for all other services. (2 Cores, 7.5G Ram) > > > We are using Scalr to manage 5-10 Farms with less than 15 Servers totally. > And, we don't experience performance issues. > Will this be enough for new version of Scalr? Or we should expect > increasing load? Because, in documentation, suggested resources for > "Smaller Clusters" are higher that ours.. > https://scalr-wiki.atlassian.net/wiki/display/docs/Suggested+Hardware+Specifications > > -- > You received this message because you are subscribed to the Google Groups > "scalr-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Michael Lochead | VP of Customer Success | Scalr | [email protected] <[email protected]> | +1.415.799.7897 (o) | +1.650.787.8476 (m) -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
