uWSGI 2.0 英文学习文档：全面指南与最佳实践 - CSDN文库

需积分: 9 167 浏览量更新于2024-07-17 收藏 1.36MB PDF 举报

uWSGI 2.0是一个强大的、高性能的Web服务器和应用程序服务器，特别适用于Python、Perl/PSGI和Ruby/Rack应用的部署。这份详细的PDF文档涵盖了uWSGI的多个关键方面，适合对uWSGI有疑问或者希望深入了解其工作原理的专业开发者阅读。首先，文档的"Quickstarts"部分介绍了快速入门指南，包括针对不同编程语言（如Python、Perl、Ruby）的示例，帮助读者在短时间内设置并运行uWSGI。对于初学者来说，这是快速熟悉uWSGI的关键路径。接着，文档深入探讨了uWSGI的核心组件和安装过程，包括如何获取最新稳定版本、构建系统以及管理uWSGI服务器。这部分内容对于理解和配置uWSGI环境至关重要。文档的"Supported languages and platforms"章节列出了uWSGI支持的语言和操作系统平台，确保了跨平台兼容性，这对于开发者来说是个重要的考量因素。 "Web server integration"部分讲述了如何将uWSGI与常见的Web服务器集成，如作为后端处理程序，以便更好地融入整体的架构。 "Frequently Asked Questions (FAQ)"包含了常见问题解答，可以帮助用户解决日常遇到的问题和疑惑。 "Conﬁguring uWSGI"是文档的核心部分，详细讲解了配置选项和最佳实践，包括如何定义新的选项、解析配置文件的逻辑以及变量解析。此外，还涉及了uWSGI协议、外部守护进程和服务管理、Master FIFO、socket activation技术和启动方式（如Upstart和Systemd）的配置。这份文档不仅提供了丰富的技术细节，还强调了"Things to know (best practices and ‘issues’)"，即一些最佳实践和可能遇到的问题，为用户提供了一套完整的uWSGI使用指南。对于希望提升uWSGI性能或深入研究其内部机制的IT专业人士来说，这份英文版的学习资料是一份不可多得的参考资料。如果你具备良好的英语水平，阅读这份文档无疑将大大增强你在uWSGI领域的知识深度和技能。

uWSGI Documentation, Release 2.0

[uwsgi]

https = :9090,foobar.crt,foobar.key

uid = foo

gid = bar

chdir = path_to_web2py

module = wsgihandler

master = true

processes = 8

If you need to bind to privileged ports (like 443 for HTTPS), use shared sockets. They are created before dropping

privileges and can be referenced with the =N syntax, where N is the socket number (starting from 0):

[uwsgi]

shared-socket = :443

https = =0,foobar.crt,foobar.key

uid = foo

gid = bar

chdir = path_to_web2py

module = wsgihandler

master = true

processes = 8

A common problem with webapp deployment is “stuck requests”. All of your threads/workers are stuck (blocked

on request) and your app cannot accept more requests. To avoid that problem you can set a harakiri timer. It is

a monitor (managed by the master process) that will destroy processes stuck for more than the speciﬁed number of

seconds (choose harakiri value carefully). For example, you may want to destroy workers blocked for more than

30 seconds:

[uwsgi]

shared-socket = :443

https = =0,foobar.crt,foobar.key

uid = foo

gid = bar

chdir = path_to_web2py

module = wsgihandler

master = true

processes = 8

harakiri = 30

In addition to this, since uWSGI 1.9, the stats server exports the whole set of request variables, so you can see (in

realtime) what your instance is doing (for each worker, thread or async core).

2.1.13 Ofﬂoading

The uWSGI ofﬂoading subsystem allows you to free your workers as soon as possible when some speciﬁc pattern

matches and can be delegated to a pure-c thread. Examples are sending static ﬁle from the ﬁle system, transferring

data from the network to the client and so on.

Ofﬂoading is very complex, but its use is transparent to the end user. If you want to try just add

--offload-threads <n> where <n> is the number of threads to spawn (1 per CPU is a good value to start

with).

When ofﬂoad threads are enabled, all of the parts that can be optimized will be automatically detected.

10 Chapter 2. Quickstarts

uWSGI Documentation, Release 2.0

uwsgi --http :8080 --http-modifier1 5 --psgi myapp.pl

(remember to replace ‘uwsgi’ if it is not in your current $PATH)

or if you are using a modular build (like the one of your distro)

uwsgi --plugins http,psgi --http :8080 --http-modifier1 5 --psgi myapp.pl

2.2.4 What is that ‘–http-modiﬁer1 5’ thing ???

uWSGI supports various languages and platform. When the server receives a request it has to know where to ‘route’

it.

Each uWSGI plugin has an assigned number (the modiﬁer), the perl/psgi one has the 5. So –http-modiﬁer1 5 means

“route to the psgi plugin”

Albeit uWSGI has a more “human-friendly” internal routing system using modiﬁers is the fastest way, so, if possible

always use them

2.2.5 Using a full webserver: nginx

The supplied http router, is (yes, incredible) only a router. You can use it as a load balancer or a proxy, but if you need

a full webserver (for efﬁciently serving static ﬁles or all of those task a webserver is good at), you can get rid of the

uwsgi http router (remember to change –plugins http,psgi to –plugins psgi if you are using a modular build) and put

your app behind nginx.

To communicate with nginx, uWSGI can use various protocol: http, uwsgi, fastcgi, scgi...

The most efﬁcient one is the uwsgi one. Nginx includes uwsgi protocol support out of the box.

Run your psgi application on a uwsgi socket:

uwsgi --socket 127.0.0.1:3031 --psgi myapp.pl

then add a location stanza in your nginx conﬁg

location / {

include uwsgi_params;

uwsgi_pass 127.0.0.1:3031;

uwsgi_modifier1 5;

}

Reload your nginx server, and it should start proxying requests to your uWSGI instance

Note that you do not need to conﬁgure uWSGI to set a speciﬁc modiﬁer, nginx will do it using the

uwsgi_modifier1 5; directive

2.2.6 Adding concurrency

You can give concurrency to to your app via multiprocess,multithreading or various async modes.

To spawn additional processes use the –processes option

uwsgi --socket 127.0.0.1:3031 --psgi myapp.pl --processes 4

To have additional threads use –threads

12 Chapter 2. Quickstarts

剩余582页未读，继续阅读

zhuangd

粉丝: 11
资源: 14

最新资源