blocks|key|178762|text|wsgi+是一个非常轻便且易于使用的解决方案，再加上gunicorn，它允许我们运行任何应用程序并轻松扩展它。Nginx在处理请求方面做得更好，因为它不像Apache那样为每个请求生成新的进程。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|178763|我已经写了一个关于如何使用nginx部署django的相关问题的答案：|178764|Deploying+Django+project+with+Gunicorn+and+nginx|178765|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/20163233/deploying-django-project-with-gunicorn-and-nginx/20529091#20529091^0|Q|8|18|1H|0|0|Z|0|0|1C|0|1C|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@$9|12|A|13|1|14]]|E|$]]|$1|J|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

Nginx is a really light and easy to use solution and along with gunicorn it allows us to run any wsgi application and scale it easily.
Nginx is better at handling requests since it does not spawn a new process for every request unlike Apache.

I have written an answer on how to deploy django with nginx for a related question:

<a href="https://stackoverflow.com/questions/20163233/deploying-django-project-with-gunicorn-and-nginx/20529091#20529091">Deploying Django project with Gunicorn and nginx</a>

blocks|key|178770|text|我有很好的使用nginx和gunicorn的经验。当我最终把所有的设置都设置好并让它运行时，它们仍然工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|178771|对于nginx和gunicorn，它们是：|178772|*+nginx+configuration+files+(/etc/nginx/sites-enabled/+and+/etc/nginx/nginx.conf)
*+gunicorn+configuration+files+(/etc/init/gunicorn.conf+and+/etc/gunicorn.d/)+|code-block|syntax|javascript|178773|我看过apache+%2B+mod_wsgi的教程，它的设置似乎要简单得多。|178774|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I have good experience with nginx and gunicorn. They keep on working great when I've finally set all the settings right and got it running.

For nginx and gunicorn they are: 

<pre><code>* nginx configuration files (/etc/nginx/sites-enabled/ and /etc/nginx/nginx.conf)
* gunicorn configuration files (/etc/init/gunicorn.conf and /etc/gunicorn.d/) 
</code></pre>

I've seen a tutorial for apache + mod_wsgi and it seems so much simpler to set up.

blocks|key|180191|text|那么，使用Nginx所用的几毫秒时间对于其他进程所花费的时间不会有多大的影响。Nginx可能会节省内存，但只有在内存很少的服务器上才会有很大的不同。对于大型网站的具体使用，可能会有一些更显着的差异，但这将成为专家的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|180192|对于大多数人来说，真正的区别可能是学习的简易性。我并不觉得Apache特别难用，而且文档也很干净。然而，我发现的大多数Python教程都是关于在Gunicorn中使用Nginx的。|180193|如果你已经知道如何在Python中使用Apache，那么使用它可能会更直接，除非你也想学习Nginx来提高你的简历。|180194|但是，如果你是一个新手，有更多关于Nginx+with+Python的文档。这使它成为更容易的选择。|180195|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Well,the few milliseconds you get with Nginx will not make a hudge difference regarding the time other processes take. Nginx may save RAM but it would only be a great difference on servers with a few RAM. For specific uses on big website there could be some more notable differences but this will become an expert affair then.
The real difference for most is probably the ease of learning. I don't find Apache to be specifically hard to use and the doc is clean. However most of Python tutorials I found are about using Nginx with Gunicorn.
If you already know how to use Apache with Python it would probably be more straight to the point to use it, unless you want to learn Nginx too to improve your CV.
However, if you are a newcomer, there is more documentation about Nginx with Python. It makes it the easier option.

blocks|key|3004344|text|我主要使用nginx和gunicorn。我目前正在使用apache+%2B+mod_wsgi。如果您的Python版本是2.7，这实际上很容易，因为当直接从包管理器安装mod_wsgi时，它将正常工作。但是如果您的代码是在不同的Python版本中。mod_wsgi必须从具有相同版本的源代码构建。如果您的Python也是从源代码安装的，那么让整个web应用程序正常工作的过程是相当困难的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3004345|另一方面，Nginx和gunicorn没有任何版本问题，因为proxypass参数使得将请求转发给gunicorn变得很容易。我们所需要做的就是确保gunicorn运行的Python版本与您的代码所在的版本相同。|3004346|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I have primarily worked with nginx and gunicorn. I am currently working with apache + mod_wsgi. It is actually easy if your Python version is 2.7 because mod_wsgi when installed directly from the package manager will work normally. But if your code is in a different Python version. mod_wsgi has to be built from source with the same version. If you installed your Python also from source then the procedure to get the whole web application working is fairly difficult.
Nginx and gunicorn on the other hand do not have any version issues, since the proxypass param makes it easy to forward requests to gunicorn. All we need to ensure is that gunicorn is running with the same version of Python that your code is in.

I want to deploy a django site (it is the open source edx code on github).

I am faced with choosing between using

<ol>
<li>Apache with mod_wsgi</li>
<li>nginx with gunicorn</li>
</ol>

I have used Apache with mod_wsgi and it's cool enough, but i have no experience with the second option.

Which of these would be a better option in terms of speed and also to some extent, ease of use?

NB: I would need to run two different django sites on say, port 80 and 81 and access them from two different subdomains.

Apache + mod_wsgi vs nginx + gunicorn

包管理器

服务器

Python

我想部署一个django站点(它是github上的开源edx代码)。我面临着在使用Apache，带mod_wsginginx，带gunicorn我在mod_wsgi中使用过Apache，这已经足够酷了，但是我没有使用第二种选择的经验。在速度和易用性方面，哪种选择更好？注:我需要在端口80和81上运行两个不同的djang...

问Apache + mod_wsgi vs nginx + gunicorn
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Apache + mod_wsgi vs nginx + gunicornEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Apache + mod_wsgi vs nginx + gunicorn
EN