You should also keep in mind that processing time usually includes the network transfer time. Most servers measure the time from the start of request decoding until the time the network connection is closed. Thus the time includes both CGI/PHP processing time and network transmission time. Unless all of your requests come from clients on a local high speed network, or your returned contents are very small, it will be difficult to isolate these two factors.
Jason On 8/12/02 12:54 PM Adrian Dolling ([EMAIL PROTECTED]) wrote: >That is clear now, thanks. > >If this is a critical analysis, then interpreting the processing time >field as a byte count would yield the pages consuming the most processing >time (totalled over all viewings). > >At 09:01 AM 8/12/02 -0700, you wrote: > >>I know. Analog has a processing time report that already covers this >>without any regexp, logformat or other hacks. But Dylan was asking >>about adding the processing time information to the request report for >>each request. >> >>This is what faq128 is about -- Analog does not do cross-referencing >>(multi-variate) reports because of the processing overhead (especially >>if it were to do this for many variable, much of which you wouldn't >>subsequently need). >> >>Instead, you can run a Request Report to find out which files are >>important to look at, then run Analog with a "FILEINCLUDE" command for >>each request report item and find out the processing time from the >>Processing Time report. >> >>Adrian Dolling ([EMAIL PROTECTED]; Monday, August 12, 2002 8:47 AM): >> >>> I think the question was about processing (not viewing/visiting) time. If a >processing time is stored in the log file, it would be really useful if >Analog were able to analyze it. >> >>> (I suspect one of our regexp experts could transform it into a byte count for >this purpose, but a native solution would be better.) >> >>> At 08:36 AM 8/12/02 -0700, you wrote: >> >>>>Dylan Alex Simon ([EMAIL PROTECTED]; Saturday, August 10, 2002 1:06 PM): >>>> >>>>> I would like some way to summarize the processing time per page requested, in >>>>> order to figure out which of our php pages are taking the most time to come >>>>> back. For example, a field on REQUEST report with average or total processing >>>>> time (as per PROCTIME) and the ability to sort by that field would be perfect. >>>>> Currently we just sort the log file by the time field by hand, but it would be >>>>> really nice if it were part of analog. Is there something like this? >>>> >>>>Analog does not provide cross-referencing reports like this. See >>>>http://analog.cx/docs/faq.html#faq128 for details. ----------------- [EMAIL PROTECTED] ----------------- Dr. Seuss books . . . can be read and enjoyed on several levels. For example, 'One Fish Two Fish, Red Fish Blue Fish' can be deconstructed as a searing indictment of the narrow-minded binary counting system. -- Peter van der Linden, Expert C Programming, Deep C Secrets +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/[email protected]/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
