On Nov 16, 7:17 pm, Remi <[email protected]> wrote: > -> we don't use any .htaccess file : everything goes directly to an > "httpd.conf" ===== Also have AllowOverride none in apache config to not search for .htaccess files.
> -> we don't use ORM since we don't use databases : only Webservices ===== Make sure you disable database functionality in the settings.yml http://www.symfony-project.org/reference/1_4/en/04-Settings#chapter_04_sub_use_database > -> how can I be sure that APC is well configured ? Do I have a way to > easily check if APC is working well ? ===== APC stats are available in browser via some web pages generate by APC itself. The configuration key to change the max php file size within APC: http://www.php.net/manual/en/apc.configuration.php#ini.apc.max-file-size by default is set to 1 M. Check in the cache dir if you have php files larger than 1M find . -type f -size +1000k If you have change the value of this key to something larger. Make sure you restart Apache after making the changes. > -> from what I heard, memcache and APC are not such different one from > another in term of performances. Was it a crapy advice ? We are > already using APC for the few objects we can store on cache. ==== The two are different in the way they store the cache, where APC uses local SHM cache, Memcache uses a centralized model with a single server holding the cache. When using multiple machines having a single centralized cache (may) make more sense. > -> I thought that Symfony 2 was absolutly not ready for production > environment ? Can we expect a huge performance increase (or decrease > depending the side you are :) ) ? ==== There are crazy people already using it for production, the trick is to use the stable parts of it :), and from what I understood you don't need the components that are not yet complete. According to the benchmarks published by Fabien it is faster than 1.4.x http://symfony-reloaded.org/fast Do you use the routing component, that's one of the slowest when it comes to processing? My suggestion for you is to establish some baseline measurements to see where you are, what's the best performance that you can achieve: a. measure how many requests can you do when requesting a static web page b. measure the overhead of php processing - have that page served by PHP (echo a template with symfony and separately by plain php) This way you can see if the overhead is with PHP, symfony or both. Realistically speaking a framework has quite an overhead compared to plain PHP so you can never achive the raw PHP speed with it. I remember reading somewhere about a presentation at the London Symfony Meetup on how to scale Symfony to process thousand requests per second, I don't remember the details, maybe some other member in this group can share more info about this. gabriel -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" 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-users?hl=en
