Hi.

On 08.04.2016 23:10, Daniel Wilcox wrote:
Hello, it might help to see your nginx config -- or the relevant bits of it. Have you adjusted nginx worker parameters at all? Not seeing any change sounds strange.


Sure.

The nginx config is as follows:

location block of the server{} (nothing interesting outside it, really - only listen/server_name and some headers):

====Cut===
location / {
    uwsgi_param REMOTE_USER $remote_user;

    include /usr/local/etc/nginx/uwsgi_params;
    uwsgi_modifier1 9;
    uwsgi_pass unix:/var/tmp/uwsgi-ftp.sock;
}
====Cut===

general and http blocks:

====Cut===
user www;
worker_processes 16;
worker_rlimit_nofile 32768;

error_log /var/log/nginx/error.log;
pid /var/run/nginx.pid;

events {
    worker_connections 8192;
    use kqueue;

    kqueue_events 8192;
    kqueue_changes 8192;
}

sendfile on;

tcp_nodelay on;
tcp_nopush on;

gzip on;
gzip_min_length 1000;
gzip_proxied any;
gzip_comp_level 3;
gzip_types text/plain text/css application/xml application/x-javascript application/javascript;

client_max_body_size 50m;
large_client_header_buffers 8 16k;

proxy_next_upstream error timeout invalid_header http_500 http_502 http_503 http_504;

proxy_headers_hash_max_size 1024;
proxy_headers_hash_bucket_size 128;

proxy_buffers 16 32k;
proxy_buffer_size 128k;
proxy_busy_buffers_size 256k;

reset_timedout_connection on;

open_file_cache max=1000 inactive=20s;
open_file_cache_valid 30s;
open_file_cache_min_uses 2;
open_file_cache_errors on;
keepalive_requests 200;
keepalive_timeout 15;

server_names_hash_max_size 1024;
====Cut===


and that's pretty much all of it.

Thanks.
Eugene.
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to