大网数据广告活动
服务器运维问答

Why is Nginx FastCGI cache STALE response slower than HIT response?

· 52CE 我爱测

I have strange problem with nginx microcache. When nginx serve STALE content, it takes too long. My actual microacha part in config: ... fastcgi_cache biznisto.sk; fastcgi_cache_bypass $skip_cache; fastcgi_cache_key "$scheme$requ…

问题原文

原帖链接 · Andrej Szabo · CC BY-SA 4.0

I have strange problem with nginx microcache. When nginx serve STALE content, it takes too long. My actual microacha part in config:

...
fastcgi_cache biznisto.sk;
fastcgi_cache_bypass $skip_cache;
fastcgi_cache_key "$scheme$request_method$host$request_uri$rt_session";
fastcgi_cache_valid 200 301 302 5m;
fastcgi_cache_use_stale updating error timeout invalid_header http_500;
fastcgi_cache_lock on;
fastcgi_cache_revalidate on;
fastcgi_cache_background_update on;
fastcgi_pass_header Set-Cookie;
fastcgi_pass_header Cookie;
fastcgi_ignore_headers Cache-Control Expires Set-Cookie;
add_header X-Cache $upstream_cache_status;
...

Screens STALE - wait 565ms HIT - wait 59ms

Any suggestions? Thanks

已采纳解答

原帖链接 · luigif · CC BY-SA 4.0

The fastcgi_cache_background_update directive allows updating an expired cache item while the stale cached response is being returned to the client.

If, however, the response is fully returned, but updating is not yet finished, it will delay subsequent actions, including processing of additional requests on the same connection, and/or the closing of the connection.

This behaviour ensures that:

  • a client cannot impose uncontrolled load on the server, assuming various limitations like limit_conn are in place
  • the overall operation is usually better and, in the worst case, is not worse than without background update.

https://trac.nginx.org/nginx/ticket/1329

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2018-04-10)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。