Thanks! That is a good idea. So Nginx will do some work to fill these variables only in their corresponding locations? Best regards, Dmitriy Shalashov 2015-05-27 17:53 GMT+03:00 Maxim Dounin <mdounin@mdounin.ru>: > Hello! > > On Wed, May 27, 2015 at 05:08:52PM +0300, Дмитрий Шалашов wrote: > > > Hi! > > > > Is there a way to measure time Nginxby skaurus - Nginx Mailing List - English
Hi! Is there a way to measure time Nginx takes to process request? Not $request_time, but rather something like "time between request was fully read and request is ready to pass it to the backend". I need it to evaluate perfomance of the geoip2 module: https://github.com/leev/ngx_http_geoip2_module I need this because I've measured speed of official MaxMind Perl modules for legacy andby skaurus - Nginx Mailing List - English
Hi! Is there a way to measure time Nginx takes to process request? Not $request_time, but rather something like "time between request was fully read and request is ready to pass it to the backend". I need it to evaluate perfomance of the geoip2 module: https://github.com/leev/ngx_http_geoip2_module I need this because I've measured speed of official MaxMind Perl modules for legacy andby skaurus - Nginx Mailing List - English
Thanks! Turned out my code had differences with Cache::Memcached::Fast hashing anyway and I decided to fix them while also moving from ips to names. Best regards, Dmitriy Shalashov 2015-02-13 16:12 GMT+03:00 Maxim Dounin <mdounin@mdounin.ru>: > Hello! > > On Thu, Feb 12, 2015 at 11:11:00PM +0300, Дмитрий Шалашов wrote: > > > > Just use names in the conby skaurus - Nginx Development
> Just use names in the configuration. You mean local DNS? Best regards, Dmitriy Shalashov 2015-02-12 17:53 GMT+03:00 Maxim Dounin <mdounin@mdounin.ru>: > Hello! > > On Thu, Feb 12, 2015 at 05:19:46PM +0300, Дмитрий Шалашов wrote: > > > Ok, thanks. > > > > Can you imagine any other viable way to pass some information to each > > serveby skaurus - Nginx Development
Ok, thanks. Can you imagine any other viable way to pass some information to each server? It doesn't need to change between server restarts. I may use a distinct variable for each of them but this seems ugly and error-prone... In case you are curious why would I need this, let me explain. Upstream directive support "hash consistent" method and in that case it uses `ketama` algorithm. Tby skaurus - Nginx Development
Hi! As far as I see Nginx have limited number of possible server parameters inside upstream block. It is enforced by function ngx_http_upstream_server for example. Now, having my own upstream module how can I approach the task of adding a couple more parameters to a servers inside it? I would like to find a solution without resorting to patch Nginx source code, resilient to Nginx updates (self-cby skaurus - Nginx Development