• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Managing Moodle Performance Testing 	Paul Stevens
 

Managing Moodle Performance Testing Paul Stevens

on

  • 95 views

Managing Moodle Performance Testing Paul Stevens

Managing Moodle Performance Testing Paul Stevens
Presented at Edinburgh Moodlemoot 2014
www.moodlemoot.ie

Statistics

Views

Total Views
95
Views on SlideShare
95
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Managing Moodle Performance Testing 	Paul Stevens Managing Moodle Performance Testing Paul Stevens Presentation Transcript

    • Moodle Load Testing Presented by Paul Stevens // 17 April 2014
    • Who am I? ●Originally a Sysadmin ●10 years of Biometrics and Telco Developments ●3.5 Years with Catalyst ●First project was delivering Totara LMS ●Delivered several Moodle Infrastructures from 200 – 2 Million Users ●Now MD of Catalyst's Europe Office
    • How size do we need our Moodle Infrastructure, how much will it cost? ●What Set-up do we need? ●Need best estimate of: –Number of users –Number of courses –Number of plug-ins/Customisations –Redundancy Requirements –Access Requirements –Number of concurrent users
    • But what is a Moodle concurrent user? ●Most common contracted measurement - however it has the least clear definition ●What “Concurrent Users” has meant on real projects: –Number of Logged in users at the time –Number of Logged in users over a time period –Users completing a SCORM or specific task –Number of concurrent views according to Google Analytics –Users viewing a page at that second (Page Views)
    • To size your system 'Concurrent User' requirement must be Defined! ●Decide how you are going to measure it –My Favourite is Page Views ●Do your best to predict –User usage patterns –Type of usage on the system –Guess at load increase –over time ●Devise a best guess peek ●Add a margin of error
    • Most common ways to implement a Moodle ●Bare Metal Internal infrastructure ●Internal Shared Virtualised infrastructure – VMware or KVM ●Outsourced Infrastructure – Bare Metal or Cloud ●Outsourced Turnkey Solution with a Moodle Partner most set-ups the Moodle Database Set-up is the Performance Achilles Heal
    • Load Testing
    • Setting up the load test ●Build your Chosen Environment, preferably with every element ●Tune everything as best you can ●Automate your scripts, so you can repeat many times – we use Jmeter and Bees with Machine guns ●Test from the networks your users use ●Set-up your monitoring ●Record your results and your monitoring
    • Find the Bottleneck.. Fix.. Repeat..
    • Setting up the load test ●Build your Chosen Environment, preferably with every element ●Tune everything as best you can ●Automate your scripts, so you can repeat many times – we use Jmeter and Bees with Machine guns ●Test from the networks your users use ●Set-up your monitoring ●Record your results and your monitoring
    • Ways to tweak to make Moodle to perform better.. ●More hardware ●More bandwidth ●Better code ●A better Software stack ●A better hardware configuration ●Tweaking the Software stack ●And runs tests again..
    • How to deal with the Political Pressure. ●Are you sure it wont crash and burn? ●We need to Launch tomorrow.. ●Why do you need to spend so much time testing? ●The Definition of 'Concurrent Users' is wrong it should be..
    • Our Preferred Set-up for Performance ●Ubuntu Linux ●Niginx ●PHP-FPM ●APC ●Postfix for the DB What to look out for: ●Lack of RAM ●Bad disk IO ●Network Latency ●Poorly tuned DB servers ●Lack of PHP accelerator
    • Questions?