ChristianGfK

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe]
@="C:\\Program Files (x86)\\Google\\Chrome Dev\\Application\\chrome.exe"
"Path"="C:\\Program Files (x86)\\Google\\Chrome Dev\\Application"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Chrome]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Chrome\.exe]

ChristianGfK

Nginx FastCGI response buffer sizes

By default when Nginx starts receiving a response from a FastCGI backend (such as PHP-FPM) it will buffer the response in memory before delivering it to the client. Any response larger than the set buffer size is saved to a temporary file on disk. This process is also explained at the Nginx ngx_http_fastcgi_module page document page.

Since disk is slow and memory is fast the aim is to get as many FastCGI responses passing through memory only. On the flip side we don't want to set an excessively large buffer as they are created and sized on a per request basis (i.e. it's not shared memory).

The related Nginx options are:

• fastcgi_buffering appeared in Nginx 1.5.6 (1.6.0 stable) and can be used to turn buffering completely on/off. It's on by default.
• [fastcgi_buffer_size](http://nginx.org/en/