w.r.t. your point 3, symfony modules do sometimes require a one-off command to re-generate cached data after a deploy of new code. an example of this is the as

w.r.t. your point 3, symfony modules do sometimes require a one-off command to re-generate cached data after a deploy of new code. an example of this is the assetic asset manager. during development you can tell assetic to compile assets dynamically, but when you do a deploy to live, you generally run: php app/console assetic:dump --env=prod if your app is configured properly this will take all css and js and compile/minify for production. it's a bit of extra "work", but well worth it for the performance benefit. so yes, it does appear that performance measurements being shown are comparing apples to oranges. however, if developers are willing to go through the extra steps to get this working, it wouldn't be out of line with other symfony framework practices.