• Save
Drupal Cafe - Nenäpäivä Technical Details
 

Drupal Cafe - Nenäpäivä Technical Details

on

  • 980 views

Janne Alho's presentation about Nenäpäivä (red nose day / comic relief) technical implementation on Drupal Café held on December 10th, 2013.

Janne Alho's presentation about Nenäpäivä (red nose day / comic relief) technical implementation on Drupal Café held on December 10th, 2013.

Statistics

Views

Total Views
980
Views on SlideShare
358
Embed Views
622

Actions

Likes
0
Downloads
0
Comments
0

5 Embeds 622

http://www.exove.com 368
http://www.exove.fi 224
http://www.exove.ee 25
http://translate.googleusercontent.com 4
http://www.exove.co.uk 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

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

    Drupal Cafe - Nenäpäivä Technical Details Drupal Cafe - Nenäpäivä Technical Details Presentation Transcript

    • NENÄPÄIVÄ PERFORMANCE BOOST Janne Alho Nenäpäivä PM Project Director, Exove
    • Nenäpäivä technical view  Drupal site with  Commerce Module  Personalized teams – Team admin logins  Custom module  Donations  External interfaces handling (other team collections status)  Teams calculation  Campaign site with different campaign phases  Main event happens once a year  Main use is anonymous browsing  Main load is registered use cases (commerce and team admins)
    • Nenäpäivä campaign phases 1-3/4  Phase 1 – Site preparation, content updates  Phase 2 – Pre-campaign     Free content uploading Commerce material orders Teams creation No specific traffic peaks  Phase 3 – Campaign period  Main usage was anonymous site browsing  Campaign information, donations targets, ideas how to help  Team donations and updates  “Real time” team € collection status  3 minutes Drupal/Varnish cache  Commerce orders  Traffic peaks in anonymous browsing  Specific team pages refresh – Varnish took majority of the peaks
    • Nenäpäivä campaign phases 4/4  Phase 4 – Nenäpäivä evening  8.11. 19:00 – 24:00  Peak use  50% of all yearly traffic in one evening  Use cases:  Donations  Donations  Donations  Phase 4’ – Cleanup  After main event evening return back to normal configurations, prepare for next year
    • TRAFFIC PRE-ANALYSIS AND PEAK PREPARATIONS
    • Peak pre-analysis and preparations 1/2  Estimating main user activities  Study of previous year traffic, review of implemented changes in service and campaign feed-back  Defining service priorities  Donation capability  Generic and Team donations  Easy to use (multiple starting points, intuitive, everything works)  Donations emotional support  Who are the ones you are helping  Stories, videos, data  Teams promotions  All other features (including commerce) clearly lower priority -> Focus area clear, keep site up and donations working
    • Peak pre-analysis and preparations 2/2  Keep donations running as priority – what it means  Donation capability build with custom module (instead of as part of commerce)  No registering  Reduce Drupal load  Possibilityto use Varnish  Optimized interface towards payment system  Optimized reporting  HW boost plan  Architecture does not allow site to be distributed (due to team donations data calculations)  Main virtual server increased performance  Memory 4GB –8GB  CPU2 core -> 4 cores  Separate Varnish to own virtual machine (4GB memory, 2 CPU cores)  Disk space analysis (no need to increase, just basic log space cleanup)  Contingency plan  Shut down Commerce  Disable T eam admin login  None needed
    • Summary  Key success factors  Know your traffic  Implement architecture to fit services and traffic  Plan fox success  Plan for disaster
    • THANK YOU! Questions?