Tag performance

DrupalCon NOLA Notes. Containing Chaos with Kubernetes

Containing Chaos with Kubernetes

Why Kubernetes

  • Scenario: Many Dockerfiles and containers needed to power application (Frontend/services container and DB container)
  • Splitting the containers down, as is best practice, to make them more ephemeral
  • Many containers on same machine = single point of failure

DrupalCon NOLA Notes. The Future of Drupal Performance - Parallel Worlds

The Future of Drupal Performance - Parallel Worlds

We load:

  • Service container
  • All the classes

We run:

  • Session intialization
  • Authorization
  • Routing

We always start from zero (even though we cache a lot)

Not necessarily bad, just how the CGI model works. It means we do potentially unecessary work.

DrupalCon NOLA Notes. Handling Powerball Night with Patch

Handling Powerball Night with Patch

  • Runs on ‘decapitated’ Drupal
  • A back-end content platform and a front-end web platform
  • Communicates via services
  • Programatic cache clearing on content deployment

DrupalCon NOLA Notes. How Puppet Labs Runs on AWS

How Puppet Labs Runs on AWS

  • Amazon EC2 offers a T2 server which allows burst capacity based on CPU ‘credits’