I just finished reading this post: https://developer.yahoo.com/performance/rules.html#flush and have already implemented a flush after the top portion of my page loads (head, css, top banner/search/nav).
Is there any performance hit in flushing? Is there such a thing as doing it too often? What are the best practices?
If I am going to hit an external API for data, would it make sense to flush before hand so that the user isn’t waiting on that data to come back, and can at least get some data before hand?
The technique described looks nice, but has several pitfalls:
1) the time between PHP script start and end is small compared to transmission time; also, this saves the user about 0.5 seconds, according to your source. Is that a significant amount of time for you?
2) this technique doesn’t work with gzip output buffering
3) if you flush too often, you’ll be sending an almost-empty packet on flush, which might actually increase loading time (on slow, noisy connections).
4) once you flush, you can’t send any more headers
5) (minor issue) the server response will come in chunked encoding, which means the client won’t know the size in advance (therefore won’t display ‘x% done’ when downloading a file).
On the other hand, if you expect your script to run for a loooong time (20+ seconds), it may be needed to send some data (spaces, for example) to keep the browser from timing out the connection.