How many WordPress instances can i run on Google Compute engine in a single google cloud platform project.

i was wondering if anyone knows how many instances of a WordPress site i can potentially run on a n1-standard-4 vm instance on the google compute engine either using compute engine or the container engine with docker. is there a way to run benchmarks to figure this out.

  • Jenkins run external script with docker command
  • Error when running SparkApp from docker container against Spark running in another container
  • How many gunicorn workers in a loadbalanced dockerized Flask app?
  • Docker : Installing Docker behind a proxy on CentOS 7 : Error while pulling image
  • Running Weston in a Docker container
  • Docker increase disk space
  • Spring MVC - String Parameter with '-' resolved as '?'
  • Will istio add support for docker swarm?
  • Have created a docker that installs nginx, python, uwsgi and django. How do I test it within a VM?
  • docker command from the running docker / process
  • How to Setup a Docker Tomcat Container on Mac OS X
  • Docker - nginx proxy - access hosts between containers
  • One Solution collect form web for “How many WordPress instances can i run on Google Compute engine in a single google cloud platform project.”

    An easy way to get a rough estimate for Google Container Engine would be to run the WordPress tutorial with a minor modification: in the cluster create command, use --machine-type=n1-standard-4. Then after following the guide to spin up a replication controller-backed wordpress pod, scale it by running

    kubectl scale rc wordpress --replicas=100

    and see how many replicas get scheduled. Keep in mind that this will just give you a rough estimate of how many instances you can run on an n1-standard-4 gated by cpu/memory. If you actually wanted to run multiple WordPress instances with persistent storage backing, you would follow this guide and repeat n times for as many as you want.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.