Hello, I have done a small benchmark with routing implementation with sf1.2 and sf1.3.
I have created 4 cache files with 500 routes in each files. - test 1 : symfony 1.2 , routing.yml.php - object creation in an array - test 2 : version "cache" symfony 1.2, serialized array with compiled routes from test 1 - test 3 : version swOptimizeRoutesPlugin : array of serialized routes - test 4 : version symfony 1.3, a big array Here the result (I have been running this test with php5.3 / macport): # TEST 1 : sf1.2 / sfPatternRouting - object creation # TEST 1 - file size: 398576.000000, include time: 0.022773, memory: 2544656 # TEST 2 : sf1.2 / sfPatternRouting - object deserialization as if cache is enabled # TEST 2 - file size: 398576.000000, include time: 0.032223, memory: 5787200 # TEST 3 : sf1.2 / swOptimizePatternRouting - array with serialized route informations # TEST 3 - file size: 426672.000000, include time: 0.004196, memory: 2183944 # TEST 4 : sf1.3 / sfPatternRouting like - full array # TEST 4 - file size: 652672.000000, include time: 0.036927, memory: *9573008* Test file : http://trac.symfony-project.org/browser/plugins/swOptimizeRoutesPlugin/trunk/test/performance/load_data.php My first conclusion is that sf1.3 take more memory than any other implementations without any speed gain. Of course I might missing something important ... my 2cents Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
