Thanks, thats great to know :) I'm actually giving eaccelerator a go as we speak, just setting up php.ini now...
As for caching, I've not got very much experience in this, but I suspect that in this app it might not do that much good. I've got memcached up on the server, and was looking at caching the db requests and maybe some function calls/pages. The app is essentially a game where every request effects the next. I suppose we could cache each user's stats and but it would only be valid for 1-2 page calls at best...Would anyone think this is still worth caching? For such a short period? I'm probably going to give it a go anyways and see what performance increase I can get, but any hints/advice would be greatly welcomed :) Mat -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Staver Sent: 08 February 2008 17:27 To: symfony users Subject: [symfony-users] Re: DB connections without Debug toolbar I saw a tenfold increase in the speed of my Symfony apps by enabling eaccelerator. I my company we use this on several servers and I haven't had any problems with it. It just sits there in the background and makes everything MUCH faster. I did some benchmarking of uncached pages vs cached pages. If I cached away all components accessing the database the speed increased from 70 requests per second to 300. With the amount of hits you have even a cache with a very short expiry time would help significantly. In my benchmarking I didn't see much performance improvement by disabling parts of Symfony. The two most significant speed increases were from enabling eaccelerator and from caching away database requests. On Feb 8, 3:50 pm, "Mat" <[EMAIL PROTECTED]> wrote: > Thanks, we are indeed Mysql based, > > Can you recommend any specific PHP accelerator? Are any easier to setup than > others, and do any perform any better than other, open source is always > preferred :) > > I'm going to look into the mysql logging it isn't something I've tried > before, so this could be interesting.... > > The App only has about 2-3 key pages, so tracking down slow queries isn't an > issue, this is why we didn't optimise it from the start, as we always felt > we could track it down onsite quickly after we had traffic, just didn't > expect this much traffic this quickly....It is also why I have still to > setup caching.....:$... now is probably the time to do it. > > Mat > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > > On Behalf Of Fabian Lange > Sent: 08 February 2008 13:28 > To: [email protected] > Subject: [symfony-users] Re: DB connections without Debug toolbar > > Hi, > installing a PHP accelerator brings a huge benefit. > Besides that I would recommend that you turn on the logging in mysql > (assuming that you use it:-)) > > Let it log all queries that are slow and those not using indices. > If you are bold you can even log all queries that are going to the db. > > Then make a tail -f onto the logfile and let users use the app. It helps to > resolve the top issues very quickly (assuming that you either know which > queries could come from what action/page, or your app is not very large so > you can find out from the query which line of code resulted in that query) > > .: Fabian > > -----Original Message----- > From: > [EMAIL PROTECTED] > om > [mailto:[EMAIL PROTECTED] > groups.com] On Behalf Of Mat > Sent: Freitag, 8. Februar 2008 13:50 > To: [email protected] > Subject: [symfony-users] DB connections without Debug toolbar > > Hey all, > > I'd quite like to increase the speed of my website (facebook app), as we are > experiencing what I class as high loads (18k hits/hour), and the strain on > load times is starting to tell, and its only getting worse (10-20% growth > daily). > > I've got a quick question, I would typically use the debug toolbar to work > out the number of database queries per page, however as this is javascript > based it isn't available to me...(due to facebook format). Is there any > other quick and easy way to tell the number of db queries per page so I can > optimise these. My instinct was to look through the logs however I thought I > would ask here first if there was an easier solution to getting at the debug > toolbar information without needing javascript. I'd also quite like to look > at the profiler information as well, however I suspect this isn't the issue > and my lack of join's in propel statements is. > > Also any other tips for easy optimisations? The plan was to install a php > optimiser as well, and also to try and disable some of the symfony code > which isn't needed, (like the helpers we don't use). > > Thanks in Advance. > Mat --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
