[Deploying Sakai] Deploy Sakai on VMs

Sam Ottenhoff ottenhoff at longsight.com
Tue Jun 10 09:36:48 PDT 2014

Well, you're adding a large new layer into your production mix that will
decrease performance while hopefully providing easier management of
resources.  If your bare machines are three years old and being replaced
with new equipment, or with faster drives (e.g., Intel enterprise SSD
drives), the impact of the virtualized IO will probably not be noticed.  If
you are deploying on the same (old) hardware, you may very well notice the
impact.  My instinct is that 75%+ of higher-ed institutions have made this
same transition over the past decade.

There was a fair bit of discussion in this thread:

On Tue, Jun 10, 2014 at 12:27 PM, Matthew Buckett <
matthew.buckett at it.ox.ac.uk> wrote:

> We currently deploy Sakai to bare machines running Debian and as part
> of a project are looking at possibly deploying to a VMware platform
> instead. Our current setup include 1 MySQL server (also running Apache
> and Solr) and 3 Tomcat workers. Does anyone have any experience
> migrating in this direction?
> Currently it's the MySQL server that is working hardest with a loadavg
> of 1.5 most of the day and MySQL is doing about 500 selects, 10
> inserts and 5 updates every second.
> We typically have between 300 and 600 active sessions (activity in the
> last 15 minutes).
> --
>   Matthew Buckett, VLE Developer, IT Services, University of Oxford
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
> TO UNSUBSCRIBE: send email to
> production-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20140610/b9dfde80/attachment.html 

More information about the production mailing list