Hello, Server side performance can be done check by reading symfony log :
- check there not too many queries (use left join) - do not use too many include partial as every time a sfPartialHelper is created. Sometime it is just fine to do an include (not nice, but in a loop this can dramatically speed your application) - Use cache - Check the code source : try to remove loop, if you work with array then try to use references, it is better to copy the array elements Client side performance : - read yahoo pages - move js at the end, avoid javascript document.write, merge js and css files, use cdn Keep in mind symfony will be never quicker that plain php. On Sat, Mar 7, 2009 at 11:49 AM, Marijn <[email protected]>wrote: > > Are we talking about perceived performance or actual performance? Most > of the time it is the front end that floors the perceived performance. > Perhaps you should have a look at this Yahoo research, it can be very > helpfull for performance improvements: > http://developer.yahoo.com/performance/rules.html > > Besides that you can turn of/strip symfony core stuff you don't need. > > Kind regards, > > Marijn > > On Mar 7, 10:43 am, Jeremy Benoist <[email protected]> wrote: > > Hi, > > > > Do you already take a look to : > http://www.symfony-project.org/book/1_2/18-Performance > > ? > > Lots of good practice to learn in this page ! > > > > Quick things I often use to improve performance : > > - use sf cache a lot ! (but cleverly) > > - use a php accelerator (APC, eAccelerator) > > - use a mify js/css > > - use a different cache than the sfFileCache (I often use > > sfSQLiteCache) > > > > Good luck :-) > > > > Jeremy > > > > On 7 mar, 08:06, Gareth McCumskey <[email protected]> wrote: > > > > > > > > > Greetings all, > > > > > We have recently released a project we have been working on for some > months > > > now as an Alpha version and while we have focussed primarily on bug > fixing > > > as well as feature completion for the next Alpha release coming up in a > > > week, I can't help but notice something disconcerting. > > > > > The project we have developed is a replacement of an existing product. > The > > > previous version, coded before my time at the company, is old, > procedural > > > and uses a very inefficient, un-normalised database structure. > > > > > For our new version, we decided to use symfony for maintainability > reasons > > > as well as the fact that this version will be a lot more complex than > its > > > predecessor so symfony's ability to simplify the development helps us > > > immensely. > > > > > The problem I have noticed is that the new symfony version seems to be > > > performing ... well ... badly. Loading pages on the new version takes a > lot > > > longer, talkin 10-50 times longer than the previous version. I went so > far > > > as to view the development logs and manually run SQL queries on our new > > > normalised database schema vs the old version un-normalised version and > the > > > new schema performs batter by a factor of 100x so I know that it is > > > definitely not the database slowing things down. I even installed > > > eAccelerator and tested the PHP processing speeds after that but have > noted > > > no significant changes. > > > > > My question .. are there any perrformance enhancements for symfony on a > > > production server that anyone can think of that might help the > situation? > > > Also, does using Ajax loaded div's contribute negatively to the > performance > > > issues? > > > > > Thanks and look forward to some tips :D > > > > > Gareth > > > -- Thomas Rabaix http://rabaix.net --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
