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

What does uwsgi_socket_keepalive affect when using the uwsgi protocol?

· 52CE 我爱测

I was looking at some options to optimize for nginx with a uwsgi upstream and noticed that at the end of the entry for keepalive the docs say: SCGI and uwsgi protocols do not have a notion of keepalive connections but there a par…

问题原文

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

I was looking at some options to optimize for nginx with a uwsgi upstream and noticed that at the end of the entry for keepalive the docs say:

SCGI and uwsgi protocols do not have a notion of keepalive connections

but there a parameter named uwsgi_socket_keepalive where the docs talk about keepalive timeout for the socket. I'm confused by this because afaik when using uwsgi socket, we default to using the uwsgi protocol. Does this imply this parameter (as well as other keepalive related parameters) are simply ignored when using the uwsgi protocol ?

已采纳解答

原帖链接 · Michael Hampton · CC BY-SA 4.0

These refer to two completely different things.

The keepalive parameter for an upstream refers to how long to keep a reusable connection open after serving a request. Some types of connections (e.g. HTTP, FastCGI) can service multiple requests on a single open connection, without closing and reopening it.

The directive uwsgi_socket_keepalive refers specifically to the TCP keepalive feature, which detects whether an open, idle connection is still alive. Though in practice, this really doesn't make a lot of sense, as a uwsgi connection isn't reusable and so it gets closed and a new connection opened with every request; it wouldn't remain idle for any significant amount of time in normal operation.

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

资料来源与适用范围

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

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

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