Roberto De Ioris <roberto@...> writes:
> What happens if you add
>
> lazy = true
>
> to your config ?
It works, that's what happens. :) Responds to requests, and the first outside
request returns in 67 milliseconds according to curl -w '%{time_total}'. Cool!
Two questions on how effective this prewarming is:
a) while a worker is reloading (e.g. due to max-requests or reload-on-rss) does
uwsgi master know to issue requests only to other workers, so that no request
in that instance is delayed waiting for the reloading worker?
b) while entire instance is reloading (e.g. due to SIGHUP), does uwsgi notify
the downstream webserver/load-balancer of the start and end of the reload, so
that the load-balancer can prefer its other upstreams while this one reloads?
- G.
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
