>> it's not until we hit real load that we see the >> site slowing down.
That suggests the site is not memory or database IO bound...maybe... But it is surprising how quickly big pages can fill your pipes (LOL) but its something that is easily overlooked and easy to calculate. Especially if the hoster is sharing out your skinny pipe.... my 5C =k= On Tue, 07 Oct 2008 14:45:31 +1300, Dmitry Ruban <[EMAIL PROTECTED]> wrote: > > Are you talking about profiling php or the whole server? Php code itself > could be only one of the possible reasons. > > > Nick Le Mouton: >> The problem is we do all our debugging and profiling on a development >> server anyway, but it's not until we hit real load that we see the >> site slowing down. It's hard to replicate real load in a development >> environment. >> >> On Oct 7, 12:10 pm, Dmitry Ruban <[EMAIL PROTECTED]> wrote: >>> Hmm, I'd suggest to do debugging and profiling on a test server not on > a >>> live. This is the common practice. >>> >>> Nick Le Mouton: >>> >>>> What does everyone use for their profiling? I'm wanting to find what's >>>> causing my site to be slow. So far the only solution I can find is >>>> installing Zend Platform, but it's not something that I can use long >>>> term (as it costs big $$$). >>>> >From what I'm reading APD and XDebug seem fine for development >>>> environments but won't work well in production (with millions of page >>>> views per day). >> > >> > > > --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
