I use this function to produce a small speed test in my pages since I run my website from my home computers.
.. webpage data goes here ..
printf("%s seconds to produce (%skb/sec)",
Note: don't forget the "speed" depends on how quick the content is actually generated and not on the speed the data is sent to the client..
However it would be good to see such function to get the real speed. :)
(PHP 4 >= 4.0.2, PHP 5)
ob_get_length — Retourne la longueur du contenu du tampon de sortie
Retourne la longueur du contenu du tampon de sortie.
Valeurs de retour
Retourne la longueur du contenu du tampon de sortie si la
tamporisation est activée, et
Exemple #1 Exemple avec ob_get_length()
echo "Bonjour ";
$len1 = ob_get_length();
echo "le monde";
$len2 = ob_get_length();
echo $len1 . ", ." . $len2;
L'exemple ci-dessus va afficher :
If you don't buffer your output, it doesn't seem like it would be possible for a web server to output a Content-Length header. For static files it can check the filesize, but for dynamic files that send output a little by little there is no way to know how many bytes it is going to output. And the headers have to be sent before a single byte is output.
Also if you're wondering why the Content-Length is important, the browser doesn't close the connection as long as the script is running. So if you register time consuming shutdown functions, the browser will still 'spin' waiting for more content until they complete. (I'm not sure this happens under all conditions, but I am certain the sending the Content-Length always prevents this.)
You might take note that this manual page does not currently output any Content-Length header.
Alternatively using mb_strlen($output, 'latin1') seems to work to determine bytes in a string. strlen may or may not depending on if it has been set up as a multibyte or not.
> Dude, your web server will compute Content-length for you!
I've noticed that Apache 1.3 doesn't do that.
However, if you’re running Apache 2.2 (and maybe 2.0, haven't experienced that yet) you don't need to worry about Content-Length.
There is a work-around for the situation you need to get length of the gz-ed buffer.
... output the page content...
ob_end_flush(); // The ob_gzhandler one
ob_end_flush(); // The main one
more info at http://www.edginet.org/techie/website/http.html
It's interesting how ob_start("ob_gzhandler"); or ob_gzhandler(); affect this function. The returned size is the buffer uncompressed size; therefore something like strlen(ob_get_contents()); just (hopefully) faster. However in order to obtain the compressed buffer size; there seem to be no function around.