Profiling web applications...
Posted: Fri Jul 15, 2005 7:13 pm
Some of my applications are starting to really grow; preformence isn't degrading yet, but I think I need to start gathering some profiling data, just in case.
I've always have some simple php timing functions I can turn on when I want to measure the time it takes for a given pages and/or sections of pages to complete. However these don't really capture concurrent load issues and that's what I'm worried about.
Last year I was looking into added some extra profiling data to my queries, as described in this thread, but I haven't had a chance to finish the design let alone implement it.
My sites tend to be split between one web server and one database server, in case that matters for your advice.
Any suggested mechanisms for attacking this?
I've always have some simple php timing functions I can turn on when I want to measure the time it takes for a given pages and/or sections of pages to complete. However these don't really capture concurrent load issues and that's what I'm worried about.
Last year I was looking into added some extra profiling data to my queries, as described in this thread, but I haven't had a chance to finish the design let alone implement it.
My sites tend to be split between one web server and one database server, in case that matters for your advice.
Any suggested mechanisms for attacking this?