hi,
i currently dev a module which makes multi subrequest sequently in the
access phase handler, via returning NGX_AGAIN.
my question is, will this kill the performance? and how far could it go
in
killing performance.
thx!
Abioy
hi,
i currently dev a module which makes multi subrequest sequently in the
access phase handler, via returning NGX_AGAIN.
my question is, will this kill the performance? and how far could it go
in
killing performance.
thx!
Abioy
On Sat, Sep 24, 2011 at 10:47 PM, Abioy S. [email protected] wrote:
hi,
i currently dev a module which makes multi subrequest sequently in the
access phase handler, via returning NGX_AGAIN.my question is, will this kill the performance? and how far could it go in
killing performance.
NGX_AGAIN is usually for non-blocking I/O operations, it’s key for
good performance under high concurrency levels.
Regards,
-agentzh
hi,
NGX_AGAIN is usually for non-blocking I/O operations, it’s key for
good performance under high concurrency level
in fact, that’s what i’m doing. but i also doubt if the main request
wake up
every time an event arrived(made by not only subrequest), will it spent
most
of the time doing sth useless?
thx
Abioy
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs