Raju Ginni

wordpress tutorials seo hosting etc

You are here: Home / nginx server tutorials (installation, configuration, performance tuning, security) / nginx upstream response is buffered to a temporary file

nginx upstream response is buffered to a temporary file

an upstream response is buffered to a temporary file  /var/cache/nginx/fastcgi_temp
wp-admin/post.php?post=50097&action=edit HTTP/2.0  (wordpress admin)
Problem:
response was buffered to disk instead of memory.
/var/cache/nginx/fastcgi_temp

nginx upstream response is buffered to a temporary file wordpress

especially while i am clicking on publish because response size big, its normal.

fastcgi_buffer_size 4K;
fastcgi_buffers 64 4k;

Fastcgi buffer will store responses up to 4K+64*4K=260K in memory

So when the request is out of in-memory buffer, data will be saved into files.

Don’t worry it’s not a problem.

#soluttion

1: disable write to disk
2. increase buffers but may not works.

to disable write to disk

fastcgi_max_temp_file 0;
     location ~ \.php$ {

To disable FastCGI disk buffering and get rid of all the an upstream response is buffered to a temporary file errors add this line:

fastcgi_max_temp_file_size 0;

location ~ \.php$ {
root /usr/share/nginx/html;
fastcgi_pass 127.0.0.1:9000;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_max_temp_file_size 0;
fastcgi_buffer_size 4K;
fastcgi_buffers 64 4k;
include fastcgi_params;
}

Enables or disables buffering of responses from the FastCGI server.

Syntax: fastcgi_buffering on | off;
Default: 
fastcgi_buffering on;
Context: http, server, location

This directive appeared in version 1.5.6.

 

When buffering is enabled, nginx receives a response from the FastCGI server as soon as possible, saving it into the buffers set by the fastcgi_buffer_size and fastcgi_buffers directives. If the whole response does not fit into memory, a part of it can be saved to a temporary file on the disk. Writing to temporary files is controlled by the fastcgi_max_temp_file_size and fastcgi_temp_file_write_size directives.

understanding nginx fast cgi buffers

fastcgi_buffers 8 16k;
fastcgi_buffer_size 32k;
fastcgi_buffer_size 4K;
fastcgi_buffers 64 4k;
Fastcgi buffer will store responses up to 4K+64*4K=260K in memory
proxy_buffers 16 16k;
proxy_buffer_size 16k;
Writing to temporary files is controlled by the fastcgi_max_temp_file_size and fastcgi_temp_file_write_size directives

increasing fast cgi buffers

By default, the buffer size is equal to one memory page. This is either 4K or 8K, depending on a platform.
fastcgi_buffers 8 32k;
fastcgi_buffer_size 32k;
fastcgi_busy_buffers_size 64k;
deafult values
Syntax: fastcgi_buffersnumbersize;
Default: 
fastcgi_buffers 8 4k|8k;

Syntax:fastcgi_buffer_sizesize;
Default:

fastcgi_buffer_size 4k|8k;

Context:http, server, location

 

increased to

fastcgi_buffers 16 64k;
fastcgi_buffer_size 64k;
fastcgi_busy_buffers_size 128k;

nginx: [emerg] “fastcgi_busy_buffers_size” must be equal to or greater than the maximum of the value of “fastcgi_buffer_size” and one of the “fastcgi_buffers” in /etc/nginx/nginx.conf:136

fastcgi_buffer_size 4k|8k;

first part of theresponse by fastcgit to read nginx
maximum size of the data that nginx can receive from the server at a time is set by the fastcgi_buffer_size directive
first part of the response received from the FastCGI server
the number and size of the buffers used for reading a response from the FastCGI server, for a single connection.
fastcgi_buffers 8 4k|8k;
number and size of the buffers used for reading a response from the FastCGI server, for a single connection.
8*16k=
fastcgi_busy_buffers_size 8k|16k;
fastcgi_buffers 8 4k|8k;
By default, size is limited by two buffers set by the fastcgi_buffer_size and fastcgi_buffers directives.
fastcgi_max_temp_file_size 1024m; default
Default:
fastcgi_temp_file_write_size 8k|16k;
Limits the size of data written to a temporary file at a time

proxy buffers in nginx

applies to single repsonef rom fastcgi
proxy_buffer_size 256k;
proxy_buffers 8 128k;
proxy_busy_buffers_size 256k;
proxy_max_temp_file_size 2048m;
proxy_temp_file_write_size 2048m;
out the buffer and resulting in a HTTP 500 error. In those instances you will need to increase this buffer to 8k/16k/32k
mycase: wordpress post editing is slow, and error logging nginx log.

wordpress slow and upstream response is buffered to a temporary file

solution 1: dsiable buffering to disk.
fastcgi_max_temp_file_size 0;
2
disable buffering
fastcgi_buffering off;
3
increase buffers
I’ve set proxy_max_temp_file_size to 0 and still get the warnings. I have oodles of spare memory, what should I change to utilise it and avoid this message?
we tested no error make sure check the string fastcgi or proxy buffer.