|
|
Posted by Peter Fox on 10/10/06 07:59
Following on from Jerry Stuckle's message. . .
[Top posting to annoy dimwits who can't cope with posting wherever is
most appropriate.]
You failed to answer the OP's question. He wants to know _exactly_, in
numbers and based on things like 'a lot' what the performance hit will
be. You've had two tries at it - strangely without success: Any reason
for that failure do you think?
>
>(Top posting fixed)
[But you didn't think of snipping - Duh! - Repeat after me: "Threaded
newsreader"]
>
>Yes, it can affect performance. The reason being that if you don't use
>output buffering, PHP can send data to the web server (and onto the
>client) while the page is being built. As soon as a buffer gets full,
>PHP sends it to the web server; the web server may send it immediately
>or buffer it further, but eventually it will send it to the client.
>
>Using the output buffering functions means PHP will have to buffer
>everything, then later send everything to the web server at once. Then
>the web server sends it to the client.
>
>So not only does this take more memory, it slows things down because PHP
>and the web server cannot pick the most opportune times to pass the data on.
>
>With all of that - normally it's not a significant delay, however.
>
>
--
PETER FOX Not the same since the statuette business went bust
peterfox@eminent.demon.co.uk.not.this.bit.no.html
2 Tees Close, Witham, Essex.
Gravity beer in Essex <http://www.eminent.demon.co.uk>
Navigation:
[Reply to this message]
|