64

I have a rather large and slow (complex data, complex frontend) web application build in RoR and served by Puma with nginx as reverse proxy. Looking at the nginx error log, I see quite a few entries like:

2014/04/08 09:46:08 [warn] 20058#0: *819237 an upstream response is buffered to a temporary file 
    /var/lib/nginx/proxy/8/47/0000038478 while reading upstream, 
    client: 5.144.169.242, server: engagement-console.foo.it, 
    request: "GET /elements/pending?customer_id=2&page=2 HTTP/1.0", 
    upstream: "http://unix:///home/deployer/apps/conversationflow/shared/sockets/puma.sock:/elements/pending?customer_id=2&page=2", 
    host: "ec.reputationmonitor.it", 
    referrer: "http://ec.foo.it/elements/pending?customer_id=2&page=3"

I am rather curious as it's very unlikely that the page remains the same for different users and different user interactions, and I would not think that buffering the response on disk is necessary/useful.

I know about proxy_max_temp_file_size and setting it to 0, but it seems to me a little bit awkward (my proxy tries to buffer but has no file where to buffer to... how can that be faster?).

My questions are:

  1. How can I remove the [warn] and avoid buffering responses? Is it better to turn off proxy_buffering or to set proxy_max_temp_file_size to 0? Why?

  2. If nginx buffers a response: When does it serve the buffered response, to whom, and why?

  3. Why nginx turns proxy_buffering on by default and then [warn]s you if it actually buffers a response?

  4. When does a response trigger that option? When it takes > some seconds (how many?) to serve the response? Is this configurable?

TIA, ngw.

  • 1
    I have a feeling that you are confusing buffering with caching. The buffering is the procedure that allows loading more data than allowed by memory allocation. – Slavic Jul 25 '16 at 15:32
77

1) How can I remove the [warn] and avoid buffering responses? Is it better to turn off proxy_buffering or set proxy_max_temp_file_size to 0? Why?

You should set proxy_max_temp_file_size to 0 in order to remove it. The proxy_buffering directive isn't directly related to the warning. You can switch it off to stop any buffering at all but that isn't recommended in general (unless it's needed for Comet).

2) If nginx buffers a response when does it serve the buffered response, to whom and why?

It servers immediately, but a client usually has much slower connection and can't consume the response data as fast as it produced by your application. Nginx tries to buffer the whole response in order to release your application ASAP.

See also: http://aosabook.org/en/nginx.html

3) Why nginx turns proxy_buffering on by default and then [warn]s you if it actually buffers a response?

As I already mentioned, the proxy_buffering isn't directly related to the warning. It's generally needed for optimized proxy operations and turning it off degrades performance and throughput.

Nginx only warns you when a response doesn't fit into configured memory buffers. You may ignore the warning if it's ok for you.

4) When does a response triggers that option? When it takes > than some seconds (how many?) to serve the response? Is this configurable?

It triggers when memory buffers are full. Please, look at the docs, the whole mechanism is explained: http://nginx.org/r/proxy_max_temp_file_size

You may want to increase memory buffers.

  • 5
    For #1, how does removing the size limit of temporary files prevent the buffering warning? I dont think this is correct because I have this directive set to 0 and still get warnings. – Phil May 9 '17 at 8:44
  • This answer is not clear enough, is it better for performance to set the proxy_max_temp_file_size to 0 or this is only a way to remove that warning? – Offir Pe'er Oct 20 at 9:11
13

The following configuration works fine on my server.

proxy_buffers 16 16k;  
proxy_buffer_size 16k;
  • 2
    Is the second directive redundant, i.e. the 16k in the first line is doing the exact same as the second line? – EoghanM Jul 5 '16 at 10:55
  • 1
    @EoghanM according to the docs, no. Proxy_Buffer_size (buffer, not plural) applies to the first part of the proxy server's response (aka the headers) Sets the size of the buffer used for reading the first part of the response received from the proxied server. This part usually contains a small response header. Proxy_buffers is for the rest of the response. – cde Dec 8 '16 at 18:53
  • 2
    You have saved some of my hair today. I was moving nginx from our server to a docker container and it started to be INCREDIBLY slow. This "fixed" it. Not sure if the version on our server had this on by default or not, but the one in the container definitely needed these settings. – Krystian Jan 2 '18 at 11:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.