Regarding cache one thing that you have to worry about is cache invalidation (which can grow into a really complex and ugly issue). Even if you don't use caching there are many strategies available, one that I recommend warmly is to avoid the ORM layer entirely by using memcache as intermediary storage for your data.
In any case the best course of action is to profile your web app to exactly find out where the performance bottleneck is and decide which part of the code requires optimization. Interesting presentation from Fabien regarding cache in Symfony2 that may be of interest to you: http://www.slideshare.net/fabpot/caching-on-the-edge-with-symfony2 gabriel On Sep 2, 11:25 pm, "Ivo Az." <[email protected]> wrote: > My local machine CPU usage goes up to max, don't know about hosting's > CPU usage, but the response times on there are the same. > > Luckily for this project the frontend changes only when something is > changed from the backend, so I will work on the caching now. > > However, my next project will be a social network, planning on > thousands of users being online. So I still need help with this, > because the cache will not be the option there. -- 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
