Welcome! Log In Create A New Profile

Advanced

significance of client_body_buffer_size as opposed to piping to upstream right away?

Posted by attozk 
significance of client_body_buffer_size as opposed to piping to upstream right away?
November 05, 2014 12:17PM
I am trying to understand the reason for buffering incoming request (client_body_buffer_size) in which nginx would either keep request in memory or write to file client_body_temp_path (based on request size).

What are the performance advantages and/or technical challenges to such an approach as opposed to piping directly (even for smaller requests) to unbuffered piping to remote server e.g. http://tengine.taobao.org/

Please share your thoughts.

Thanks
Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 181
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready