Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Scaling PHP

Scaling PHP

Scaling PHP presented at PHPBulgaria 2016

Dustin Whittle

October 08, 2016
Tweet

More Decks by Dustin Whittle

Other Decks in Technology

Transcript

  1. PHP IS USED BY THE LIKES OF FACEBOOK, YAHOO, ZYNGA,

    TUMBLR, ETSY, AND WIKIPEDIA. HOW DO THE LARGEST INTERNET COMPANIES SCALE PHP TO MEET THEIR DEMAND? JOIN THIS SESSION AND FIND OUT HOW TO USE THE LATEST TOOLS IN PHP FOR DEVELOPING HIGH PERFORMANCE APPLICATIONS. WE’LL TAKE A LOOK AT COMMON TECHNIQUES FOR SCALING PHP APPLICATIONS AND BEST PRACTICES FOR PROFILING AND OPTIMIZING PERFORMANCE. AFTER THIS SESSION, YOU’LL LEAVE PREPARED TO TACKLE YOUR NEXT ENTERPRISE PHP PROJECT.
  2. AGENDA • Why performance matters? • The problems with PHP

    • Best practice designs • Distributed data caches with Redis and Memcached • Doing work in the background with queues • Http caching and a reverse proxy with Varnish • Using the right tool for the job • Tools of the trade • Xdebug + WebGrind • XHProf + XHProf GUI • AppDynamics • Google PageSpeed • Architecture not applications
  3. WHAT I HAVE WORKED ON • Developer Advocate @
 •

    Developer Evangelist @
 • Consultant & Trainer @
 • Developer Evangelist @
  4. WHEN MOZILLA SHAVED 2.2 SECONDS OFF THEIR LANDING PAGE, FIREFOX

    DOWNLOADS INCREASED 15.4% (60 million more downloads)
  5. •Performance is key to a great user experience •Under 100ms

    is perceived as reac$ng instantaneously •A 100ms to 300ms delay is percep$ble •1 second is about the limit for the user's flow of thought to stay uninterrupted •Users expect a site to load in 2 seconds •AXer 3 seconds, 40% will abandon your site. •10 seconds is about the limit for keeping the user's a*en$on •Modern applicaDons spend more Dme in the browser than on the server-side
  6. Login Flight Status Search Flight Purchase Mobile Big data SOA

    NOSQL Cloud Agile Web Application complexity is exploding
  7. session.save_handler = memcached session.save_path = "10.0.0.10:11211,10.0.0.11:11211,10.0.0.12:11211" memcached.sess_prefix = “session.” memcached.sess_consistent_hash

    = On memcached.sess_remove_failed = 1 memcached.sess_number_of_replicas = 2 memcached.sess_binary = On memcached.sess_randomize_replica_read = On memcached.sess_locking = On memcached.sess_connect_$meout = 200 memcached.serializer = “igbinary”
  8. THE BEST SOLUTION IS TO LIMIT SESSION SIZE AND STORE

    ALL DATA IN A SIGNED OR ENCRYPTED COOKIE
  9. Scaling server-side applications • Caching - Cache as much on

    the client-side and server side as possible (javascript, css, images, fonts, content). • Leverage a CDN + browser caching • Use a reverse proxy cache on the server side • Queuing - Do not delay the user experience for tasks that can be executed in the background • Async - Optimize work to execute concurrently / asynchronously
  10. •Any data that is expensive to generate/query and long lived

    should be cached •Web Service Responses •HTTP Responses •Database Result Sets •ConfiguraDon Data
  11. $memcache = new Memcache(); $memcache->connect('localhost', 11211); $memcacheDriver = new Doctrine\Common\Cache\MemcacheCache();

    $memcacheDriver->setMemcache($memcache); $client = new Guzzle\H:pClient(‘h:p://www.test.com/’); $cachePlugin = new Guzzle\Plugin\Cache\CachePlugin(array( ‘storage’ => new Guzzle\Plugin\Cache\DefaultCacheStorage( new Guzzle\Plugin\Cache\DoctrineCacheAdapter($memcacheDriver) ) )); $client->addSubscriber($cachePlugin); $response = $client->get(‘h:p://www.wikipedia.org/’)->send(); $response = $client->get(‘h:p://www.wikipedia.org/’)->send();
  12. $memcache = new Memcache(); $memcache->connect('localhost', 11211); $memcacheDriver = new Doctrine\Common\Cache\MemcacheCache();

    $memcacheDriver->setMemcache($memcache); $config = new Doctrine\ORM\ConfiguraDon(); $config->setQueryCacheImpl($memcacheDriver); $config->setMetadataCacheImpl($memcacheDriver); $config->setResultCacheImpl($memcacheDriver); $enDtyManager = Doctrine\ORM\EnDtyManager::create(array(‘driver’ => ‘pdo_sqlite’, ‘path’ => __DIR__ . ‘/db.sqlite’), $config); $query = $em->createQuery(‘select u from EnDDesUser u’); $query->useResultCache(true, 60); $users = $query->getResult();
  13. •Any process that is slow and not important for the

    h:p response should be queued •Sending noDficaDons + posDng to social accounts •AnalyDcs + InstrumentaDon •UpdaDng profiles and discovering friends from social accounts •Consuming web services like Twi:er Streaming API
  14. use Symfony\Component\H:pFoundaDon\Response; $response = new Response(‘Hello World!’, 200, array(‘content-type’ =>

    ‘text/html’)); $response->setCache(array( ‘etag’ => ‘a_unique_id_for_this_resource’, ‘last_modified’ => new DateTime(), ‘max_age’ => 600, ‘s_maxage’ => 600, ‘private’ => false, ‘public’ => true, ));
  15. use Symfony\Component\H:pFoundaDon\Request; use Symfony\Component\H:pFoundaDon\Response; $request = Request::createFromGlobals(); $response = new

    Response(‘Hello World!’, 200, array(‘content-type’ => ‘text/html’)); if ($response->isNotModified($request)) { $response->send(); }
  16. Caching Best Practices • Use consistent URLs: if you serve

    the same content on different URLs, then that content will be fetched and stored multiple times. Tip: note that URLs are case sensitive! • Ensure the server provides a validation token (ETag): validation tokens eliminate the need to transfer the same bytes when a resource has not changed on the server. • Identify which resources can be cached by intermediaries: those with responses that are identical for all users are great candidates to be cached by a CDN and other intermediaries. • Determine the optimal cache lifetime for each resource: different resources may have different freshness requirements. Audit and determine the appropriate max-age for each one. • Determine the best cache hierarchy for your site: the combination of resource URLs with content fingerprints, and short or no-cache lifetimes for HTML documents allows you to control how quickly updates are picked up by the client.
  17. •Stay up-to-date with the latest stable version of your favorite

    framework •Disable features you are not using (I18N, Security, etc) •Always use a data cache like Memcached/Redis •Enable caching features for views and database result sets •Always use a HTTP cache like Varnish
  18. •Upgrade to PHP 7 with Zend OpCache using PHP-FPM +

    Nginx •Stay up to date with your framework + dependencies (using Composer) •OpDmize your session store to use signed cookies or database with caching •Cache your database and web service access with Memcache or Redis •Do blocking work in the background with queues and tasks using Resque •Use HTTP caching and a reverse proxy cache like Varnish •Profile code with Xdebug + Webgrind and monitor producDon performance with AppDynamics!
  19. Common Performance Best Practices • Reduce size of HTTP requests

    • Optimize stylesheets + javascripts + images + fonts • Leverage gzip compression • Reduce cookie size + use cookie less domains for static assets
  20. Common Performance Best Practices • Optimize content • Move stylesheet

    to head • Move javascript to body close (and eliminate blocking javascript) • Preload components when idle
  21. Common Performance Best Practices • Reduce DNS lookups • Reduce

    network latency with Content Delivery Networks • Use service workers
  22. Understanding the impact of HTTP2 • Todays best practices are

    tomorrows anti-patterns • The limitations of HTTP/1.X forced us to develop various application workarounds (sharding, concatenation, spriting, inlining, etc.) to optimize performance. However, in the process we’ve also introduced numerous regressions: poor caching, unnecessary downloads, delayed execution, and more. • HTTP/2 eliminates the need for these hacks and allows us to both simplify our applications and deliver improved performance. • You should unshard (domains), unconcat (css/javascript), and unsprite your assets (images) • You should switch from inlining to server push • Read Ilya Grigorik awesome book on browser performance - http://hpbn.co/http2
  23. This talk is heavily inspired from: Google PageSpeed Rules Google

    Web Fundamentals Ryan Tomayko’s “Things Caches Do” Addy Osmani’s “Automating Workflow” Ilya Grigorik “High Performance Browser Networking”