3 ms·

> https://github.com/TechEmpower/FrameworkBenchmarks/blob/master/php-symfony2/src/Skamander/BenchmarkBundle/Controller/BenchController.php https://github.com/Te

> https://github.com/TechEmpower/FrameworkBenchmarks/blob/master/php-symfony2/src/Skamander/BenchmarkBundle/Controller/BenchController.php https://github.com/TechEmpower/FrameworkBenchmarks/blob/mast... Doctrine is slow, and this is not how you would use it in the real world. Throwing a cache on top of everything will speed it up considerably.

bhauer 14y ago
We have expressly avoided caching in these tests (so far) in order to exercise the ORM and database connectivity. In future tests, we plan to introduce caching [1]. If you have thoughts about specific test characteristics you'd like to see when caching is added, I'd like to hear those thoughts. Thanks for the feedback! [1] https://github.com/TechEmpower/FrameworkBenchmarks/issues/133 https://github.com/TechEmpower/FrameworkBenchmarks/issues/13...
- beberlei 14y ago
  Doctrine is explicitly not suitable for non cache usage. You should remove the ORM from the test and use the DBAL only instead if you don't have caching introduced. Additionally you are not bootstrapping the Symfony cache correctly, you need to run "php app/console cache:clear --warmup --env=prod --no-debug" before running the tests, it might cause cache slams in your benchmarks.
  - newbie12 14y ago
    Correct, running the debugging bar in Sf2 will kill performance.
- fooyc 14y ago
  At least the annotation/metadata/dql parser cache should be enabled: metadata_cache_driver: apc Else you are benchmarking the annotation and DQL parsers. Also, for big PHP frameworks you have to make sure that APC's SHM size is large enough.