Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

Handling 10k requests per second with Symfony and Varnish - SymfonyCon Berlin 2016

It is believed that the Symfony framework is quite heavy and it can be difficult to develop a website that will be able to work under the high load. It is true, but does this mean that it is impossible to implement a dynamic caching and to update only a small part of entire page as data is updated? This talk will give your an answer to that. It is Varnish, ESI-blocks and load balancing. With hundreds of thousands of unique visitors and million hits a day, we continue to use Symfony, and do not see any problems.

8.
Agenda
‣ We review briefly the process of typical
Symfony site growing

9.
Agenda
‣ We review briefly the process of typical
Symfony site growing
‣ What is Varnish and why it’s so popular

10.
Agenda
‣ We review briefly the process of typical
Symfony site growing
‣ What is Varnish and why it’s so popular
‣ How to prepare your Symfony site for
Varnish?

11.
Agenda
‣ We review briefly the process of typical
Symfony site growing
‣ What is Varnish and why it’s so popular
‣ How to prepare your Symfony site for
Varnish?
‣ VCL tricks to easily handle 10K
requests/second with Symfony

72.
Pros and cons of simple
cacheing
+ Page can be cached by Varnish, allowing for
faster responses.
+ Very simple to configure and use.
- Delays in the response time after cache expiration.
- We can not update information in the blocks
without a full page refresh.
- We need to render all 3 blocks at once.

83.
Pros and cons of async
cacheing
+ Page can be cached by Varnish, allowing for
faster responses.
+ Very simple to configure and use.
+ No delays after cache expiration.
- We can not update information in the blocks
without full page refresh.
- We need to render all 3 blocks at once.

97.
Pros and cons of async ESI
cacheing
+ Page can be cached by Varnish, allowing for faster
responses.
+ No delays after cache expiration.
+ We can update information in the blocks without
full page refresh.
+ We render and cache each block separately. This
will result in less memory usage and better hit rate.
- Can be dangerous if used without control.