Hello!
On Tue, Dec 2, 2014 at 12:57 PM, chase.holland wrote:
> Thank you for your quick response! Could you be more specific on what is
> blocking the worker process?
Just FYI: you can always find the blocking IO calls via tools like the
off-CPU flame graphs:
https://github.com/openresty/nginx-s
Valentin V. Bartenev Wrote:
---
> On Monday 01 December 2014 22:09:14 chase.holland wrote:
> > Hey all,
> >
> > We've written a module to connect NGINX / OpenResty with ZMQ
> endpoints
> > (https://github.com/neloe/ngx_zmq), but all requests thro
On Monday 01 December 2014 22:09:14 chase.holland wrote:
> Hey all,
>
> We've written a module to connect NGINX / OpenResty with ZMQ endpoints
> (https://github.com/neloe/ngx_zmq), but all requests through the module
> report a 0.000 time back to access.log, making it impossible to determine
> whi
Hey all,
We've written a module to connect NGINX / OpenResty with ZMQ endpoints
(https://github.com/neloe/ngx_zmq), but all requests through the module
report a 0.000 time back to access.log, making it impossible to determine
which of our subsystems is the problem area in terms of latency. Is ther
