MarlonBerzamina
New Member
I had a huge load on my servers yesterday, and, even if I worked on optimizing the performances before (I had a similar problem about 2 months ago), my servers couldn't handle the load (I have a service which had about 50 account creations per minute).Finally, my servers handled the load because I changed the instances : I am on Amazon EC2, and I was using a load balancer with 20 micro instances. It was not enough. I finally changed to 10 large instances, and that was OK.But, you know, large instances are kinda expensive, and I can't afford to have so much large instances (now, because there is less load, I have "only" 5 large instances running, but it is also too much).So, I am still working on the optimization and the server configuration, but I am stuck on a point.So far, I am using symfony with memcached. It works fine, everything that should be cached is cached, etc.Now, I want to add a Varnish in front of my apache web server.I did so, and I configured it - I think - well, and it is running now. The problem is that there is no hit on the cache.From what I saw, the problem is that the HTTP headers sent by symfony are not set correctly.For example, for a cached request, I have the following headers :\[code\] Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache\[/code\]The module is correctly configured to use cache, etc., but I just can't find where I can set the correct HTTP headers. I know how to set a cache header in symfony for a specific action, but clearly, I don't want to do it on every action (by the way, even if I did that, I think that this is not the right way).So I'm asking how can I use Varnish with symfony 1.4From what I saw, there are two possibilities :
- I set correctly the HTTP headers sent by symfony
- I configure Varnish to handle correctly the default HTTP headers sent by symfony