I’m recently start using NGINX in combination with my FastCGI service,
it work quite good and effective.
I decided to use pipeline as it works effectively utilizing one
connection.
According to NGINX logs pipelining is work, but I mentioned interesting
thing - NGINX passes request to FCGI in synchronous mode, i.e. it’ll
send the next request only after the first one will complete.
It’s weired for me.
Is such behavior is expected?
Maybe I miss some critical parameter in configuration?
On Tue, Mar 06, 2012 at 12:04:35PM -0500, chuda wrote:
It’s weired for me.
Is such behavior is expected?
Yes. Pipelined requests from client are processed in order. That
is, processing of next request starts only when previous requests
was handled and response sent (at least to socket buffer).
Yes. Pipelined requests from client are processed
in order. That is, processing of next request starts only when
previous requests was handled and response sent (at least to socket
buffer).
Thank you for fast response.
Is it common approach how NGINX serves pipelined requests to any
upstream module or FCGI specific?
On Tue, Mar 06, 2012 at 04:51:12PM -0500, chuda wrote:
Maxim D. Wrote:
Yes. Pipelined requests from client are processed
in order. That is, processing of next request starts only when
previous requests was handled and response sent (at least to socket
buffer).
Thank you for fast response.
Is it common approach how NGINX serves pipelined requests to any
upstream module or FCGI specific?
It’s how nginx handles pipelined requests (regardless of any
processing details).
Is there any technique to speed it up?
Use multiple connections?
Maxim D.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.