Re: map_hash_bucket_size, map_hash_max_size, and memory usage

Thanks Maxim -- that's actually the page that has led me to ask these questions. Since the content of that page is a bit general, I was hoping to get some more specific detail about how all the pieces are connected so that I could optimize my NGINX hash map setup as much as possible. Thanks for

map_hash_bucket_size, map_hash_max_size, and memory usage

I was hoping someone could clarify how exactly map_hash_bucket_size and map_hash_max_size should be set and the impact it has on memory. For map_hash_bucket_size, it says it should be a multiple of the processor's line cache size. Under what circumstances does it make sense or would it be necessar

Max File Size Allowed In Cache

Is there any way to limit the maximum size of an individual object in a proxy cache? Looking through the documentation ( http://nginx.org/en/docs/http/ngx_http_proxy_module.html ) I'm not seeing anything directly related to that. I might be misunderstanding the proxy_temp_file_write_size or proxy_

Trying to Understand Upstream Keepalive

I'm trying to better wrap my head around the keepalive functionality in the upstream module as when enabling keepalive, I'm seeing little to no performance benefits using the FOSS version of nginx. My upstream block is: upstream upstream_test_1 { server 1.1.1.1 max_fails=0; keepalive 50; } With

Re: Upstream Keepalive Questions

Maxim, Thanks so much for clarifying. Just to make sure I'm understanding correctly, if I had something like this pseudo-code upstream upstream1 { } upstream upstream2 { } upstream upstream3 { } upstream upstream4 { } upstream upstream5 { } server { server_name server1.com; proxy_pass http://ups

Upstream Keepalive Questions

I'm somewhat unclear about how the keepalive functionality works within the upstream module. My nginx install currently handles several hundred domains all of which point to different origin servers. I would imagine I can improve performance by enabling keepalive, however the documentation says "Th

More Descriptive 502 Errors

Every so often I see a handful of errors in my error log, such as: connect() failed (113: No route to host) upstream timed out (110: Connection timed out) upstream sent too big header while reading response header from upstream etc. in each case, when I log the $status variable in nginx, each ju

Re: Include Performance

Awesome -- thanks so much for the quick reply! Posted at Nginx Forum: http://forum.nginx.org/read.php?2,248331,248333#msg-248333 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Include Performance

Is there any negative performance impact with chaining include commands on nginx? For example, are any of these worse than any of the others from a performance perspective: In nginx.conf: include domain_config_1.conf; include domain_config_2.conf; OR In nginx.conf: include domain_configs.conf;

Re: Proxy returns 504 then blocks next connections

The script is an ASPX script and, to my knowledge, it doesn't use sessions. I don't control the script, but I can't duplicate the behavior when running against the proxied server. It only occurs when going through the proxy. I don't believe sessions are the issue. Posted at Nginx Forum: http://fo

Proxy returns 504 then blocks next connections

I'm having an issue where I proxy a long running script and receive a 504 error when it exceeds my proxy_read_timeout setting. All of that's behaving normally -- what isn't behaving normally is that the next several requests I make to the domain via the same proxy code also return 504s after timing

Re: Status Code 001 In Logs

Based on your post, I was actually dug a little bit deeper because there was nowhere in my Perl I could find that returned 1. After disabling most of the Perl, I was getting 499 errors which made sense, the client was closing the connection. It looks like part of the issue is that attached to the

Re: Status Code 001 In Logs

Sorry for the delay. I do think part of the issue is tied to the load balancer since that connection is timing out (we set it very low for testing purposes), but the load balancer terminating the connection doesn't explain why nginx is returning a 001 status code, since the connection from the ngin

Status Code 001 In Logs

I can't find documention anywhere on what it means when nginx shows 001 as the value of $status in the access_log. I currently use nginx as a reverse proxy and I get this error when uploading large files (2+ MB though my client_max_body_size is 4 MB) . Also worth noting, the follow values per my