Pipelining and Output buffering
Pipelining and Output buffering
- Multiple outstanding requests
- Responses are still serialized - difference is timing
- Purpose is to pack TCP segments better
- When to Flush?
- If the data in the output buffer exceeds 1K
- If the data is buffered longer than N ms
- If the application explicitly requests it
- Experimenting with Nagle’s algorithm
- Turned on/off in both client and server