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

Profiling PHP applications

Profiling PHP applications

Confoo 2014, Montreal

It's nothing new that speed is important for the success of any web application. This talk will show how you can correctly measure the performance of your site and track down bottlenecks with tools like Xdebug, XHProf or the Symfony Debug Toolbar. And if you still need to get faster after optimizing and fixing all these issues, I'll introduce you to some tricks, techniques and patterns to even further decrease load times.

Bastian Hofmann

February 27, 2014
Tweet

More Decks by Bastian Hofmann

Other Decks in Programming

Transcript

  1. Questions? Ask by the way, if you have any questions

    throughout this talk, if you don't understand something, just raise your hand and ask.
  2. but seriously, in the last years multiple studies were made

    on the importance of speed for a web application. how does it affect usage and conversion? how long are people waiting for content? how does it affect sales? if people left because the site is slow, are they coming back?
  3. ..

  4. Server the first thing the contributes to pagespeed is what

    happens on the server. this is also the easiest part, because it is completely under our control
  5. Your PHP application Request Response so what your server and

    your application is doing between incoming request and outgoing response
  6. Your PHP application Request Response Load balancer though this does

    not mean only your application, but also the rest of your setup, like a loadbalancer
  7. Your PHP application Request Response Load balancer and also your

    application is probably not a single small php script, but a big application with multiple components that each can affect speed differently. so getting a more detailed view on these components might be interesting as well. more to that later
  8. web server db http service http service cache user request

    additionally most bigger applications have some kind of a service oriented architecture, same things apply here. knowing about the speed of the different services is important.
  9. But there is more ... your application does not stop

    at your server. somehow it needs to get to your user
  10. so internet connectivity is also a big part, contributing to

    pagespeed, that means everything from dns lookup, over ssl handshake to actually transporting the content over the wire
  11. when your user received the content, he needs to display

    it. and some browsers are way slower than others in doing it
  12. and of course nearly no web application comes without javascript.

    this needs to be loaded and executed as well
  13. But the rest is as well my point is: what

    is important is the pagespeed your user perceives. this contains everything from server to his browser. in the end it's your fault if the site is slow, even if the user's computer and browser is crappy.
  14. because although everything seems to be fine on your fast,

    2 month old machine, with lot's of ram, cpu power, latest chrome, from your 50mbit vdsl connection with a very low ping to your data center.
  15. people in countries with big latencies to your datacenter and/or

    slow internet connections (rember dial up)
  16. Getting it back to the server so now you have

    all the timestamps in your javascript, you need to ...
  17. input filter output basic workflow is that you have some

    input where logstash gets log messages in, on this input you can execute multiple filters that modify the message and then you can output the filtered message somewhere
  18. Very rich plugin system to do this it offers a

    very large and rich plugin system for all kinds of inputs, filters and outputs, and you can also write your own
  19. browser JS: boomerang logstash trackingServer access log requests tracking image

    with timing information as query parameters for our purpose we can just have boomerang in the browser collect the timestamps and then send a small tracking request (inserting an image) to a tracking server. the timestamps are added as query parameters to this request. the server only returns an empty image and logs the request to his access log which logstash can parse.
  20. Graphite http://graphite.wikidot.com/ again there are many tools available to collect

    and display these metrics: one i want to highlight is graphite
  21. graphite comes with a powerful interface where you can plot

    and aggregate this data into graphs and perform different mathematical functions on it to get it exactly the way you want to display your data
  22. browser JS: boomerang logstash trackingServer access log requests tracking image

    with timing information as query parameters graphite statsd and statsd is a small load balancing daemon for it. so this is your setup logstash sends these timestamps to statsd who aggregates the information and sends them to graphite
  23. Can we measure more? I said earlier we may need

    information about services etc
  24. Load balancer in a soa architecture we can do something

    similar with the access logs of our services, which also have timing information. or if we have a load balancer (like haproxy) in between as well. we can get useful information from there
  25. browser JS: boomerang logstash trackingServer access log requests tracking image

    with timing information as query parameters graphite statsd logstash load balancer access log logstash service access log logstash can analyse these logs and send them to statsd as well
  26. From within your PHP app What is also useful is

    to measure certain things from within your php app, e.g. rendering time. time database requests took. time spent of certain business logic etc. you can either just log this to a file and use the same logstash mechanism, or if you just need to have it for debugging, do it differently. more to that later.
  27. By pages but you should not only measure all your

    request, you should differentiate by...
  28. first tool usefull for this is ... xdebug has quite

    a few functionalities like offering the ability to make breakpoints in your code, nicer error displays and so on. but one is also profiling of your app
  29. Webgrind https://github.com/jokkedk/webgrind this write so called cachegrind files. in order

    to view this you can use tools like kcachegrind or the easiest one ...
  30. you can see everything that happend in this request, every

    function that was invoked, how often this was and how long it took.
  31. Use it locally on your dev machine one thing with

    xdebug, it slows down php, so .. but not in production
  32. Use it in production for a subset of requests you

    can safely use it in production, it comes with a performance overhead but only when used, so you can activate it, but only use for a small percentage of requests or when manually activated (e.g. by a cookie).
  33. Symfony Debug Toolbar i said earlier, that there is another

    good way to get information about your applications internals, especially if you only need it for debugging and not in a graph. this is with the..
  34. you can click on it and it gives you nice

    detailed information about the request. stuff like doctrine queries, a nice timeline, exceptions, routing, events etc.
  35. Extend it http://symfony.com/doc/current/cookbook/profiler/ data_collector.html but did you know that you

    can extend it? there are some good ready made extensions available, e.g. for caching, http calls, versioning etc. just check packagist, but you can also write your own easily.
  36. here are some examples how we at researchgate extended it

    (disclaimer: we are not even using full symfony, but only some components).
  37. Step 3 now that you have all this debugging information

    to pinpoint your bottlenecks, let's get to ...
  38. That's something you have to do unfortunately ... since it

    is very dependent on your application and your setup
  39. ESI

  40. Profile Publications Publication Publication Publication AboutMe LeftColumn Image Menu <esi:include

    src="..." /> Institution because every component has it's own url you can just render out a esi placeholder instead of the widget to tell varnish to fetch it separately and provided it has caching headers, get it out of the cache
  41. Profile Publications Publication Publication Publication AboutMe LeftColumn Image Menu <div

    id="placeholder"></div> <script>loadWidget('/aboutMe', function(w) { w.render({ replace : '#placeholder' }); })</script> Institution so instead of rendering the widget you render a placeholder dom element and a script tag that loads the widget with an ajax request and then renders it on the client side
  42. pushState and if you are at that, when you switch

    pages, you can also just load the differences between and use pushState to change the url (if supported) to make your app faster
  43. if you look at your widget tree you can mostly

    identify larger parts, which are widgets itself
  44. Profile Menu Header LeftColumn RightColumn like this, so what you

    can do to dramatically increase the perceived load time is prioritizing the rendering
  45. so our http request looks like this, first you compute

    and render the important parts of the page, like the top menu and the profile header as well as the rest of the layout, for the left column and right column which are expensive to compute you just render placeholders and then flush the content to the client so that the browser already renders this
  46. still in the same http request you render out the

    javascript needed to make the already rendered components work, so people can use the menu for example
  47. still in the same http request you then compute the

    data for the left column and render out some javascript that takes this data and renders it into the components template client side and then replaces the placeholder with the rendered template
  48. still in the same request you then can do this

    with the right column -> flush content as early as possible, don't wait for the whole site to be computed