blocks|key|606162|text|这是一个难以回答的问题。如果您编写了一个真正轻量级的节点服务器来只服务静态文件，那么它的性能很可能会比nginx更好，但它并不是那么简单。(Here's+a+"benchmark"比较nodejs文件服务器和lighttpd+-在提供静态文件时，其性能与ngingx相似)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|606163|在服务静态文件方面的性能通常归结为不仅仅是web服务器在做这项工作。如果您想要尽可能高的性能，您将使用CDN为您的文件提供服务，以减少最终用户的延迟，并从边缘缓存中受益。|606164|如果您不担心这一点，node在大多数情况下都可以很好地提供静态文件。Node采用异步代码，这也是它所依赖的，因为它是单线程的，任何阻塞的i/o都会阻塞整个进程，降低应用程序的性能。你很可能是以一种非阻塞的方式编写代码，但是如果你在同步地做任何事情，你可能会导致阻塞，这将降低其他客户端获得静态文件服务的速度。简单的解决方案是不编写阻塞代码，但有时这是不可能的，或者您不能总是强制执行它。|606165|entityMap|0|LINK|mutability|MUTABLE|url|http://posterous.ngspinners.com/benchmarking-static-file-servers-lightnode-li^0|1Y|K|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

That's a tricky question to answer. If you wrote a really lightweight node server to just serve static files, it would most likely perform better than nginx, but it's not that simple. (<a href="http://posterous.ngspinners.com/benchmarking-static-file-servers-lightnode-li" rel="nofollow">Here's a "benchmark"</a> comparing a nodejs file server and lighttpd - which is similar in performance to ngingx when serving static files).

Performance in regard to serving static files often comes down to more than just the web-server doing the work. If you want the highest performance possible, you'll be using a CDN to serve your files to reduce latency for end-users, and benefit from edge-caching. 

If you're not worried about that, node can serve static files just fine in most situation. Node lends itself to asynchronous code, which it also relies on since it's single-threaded and any blocking i/o can block the whole process, and degrade your applications performance. More than likely you're writing your code in a non-blocking fashion, but if you are doing anything synchronously, you may cause blocking, which would degrade how fast other clients can get their static files served. The easy solution is to not write blocking code, but sometimes that's not a possibility, or you can't always enforce it.

blocks|key|390358|text|我不同意这里的答案。虽然Node会做得很好，但如果配置正确，nginx肯定会更快。nginx是用C语言高效实现的，遵循类似的模式(只在需要的时候才返回连接)，占用的内存很小。此外，它支持sendfile系统调用来服务这些文件，这是您在服务文件时尽可能快的速度，因为它是操作系统内核本身在做这项工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|390359|到目前为止，nginx已经成为前端服务器的事实标准。您可以利用它在服务静态文件、gzip、SSL甚至稍后的负载平衡方面的性能。|390360|附注:这假设文件实际上是“静态的”，就像请求时磁盘上的静态文件一样。|390361|entityMap|0|LINK|mutability|MUTABLE|url|http://linux.die.net/man/2/sendfile^0|2L|8|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

I'll have to disagree with the answers here. While Node will do fine, nginx will most definitely be faster when configured correctly. nginx is implemented efficiently in C following a similar pattern (returning to a connection only when needed) with a tiny memory footprint. Moreover, it supports the <a href="http://linux.die.net/man/2/sendfile" rel="noreferrer">sendfile</a> syscall to serve those files which is as fast as you can possibly get at serving files, since it's the OS kernel itself that's doing the job.

By now nginx has become the de facto standard as the frontend server. You can use it for its performance in serving static files, gzip, SSL, and even load-balancing later on.

P.S.: This assumes that files are really "static" as in at rest on disk at the time of the request.

blocks|key|390420|text|我确信纯node.js可以在很多方面胜过nginx。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|390421|所有人都说我必须留下来，NginX有一个内置的缓存，而node.js没有出厂安装(你必须构建自己的文件缓存)。自定义文件缓存确实优于nginx和市场上任何其他服务器，因为它非常简单。|390422|此外，Nginx在多核上运行。要充分利用Node的潜力，您必须将节点服务器集群化。如果你有兴趣知道怎么做，那么请在下午|390423|你需要深入挖掘，以实现与节点的性能涅盘，这是唯一的问题。一旦经历了地狱是的..。它打败了Nginx。|390424|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|$]]

I am certain that purely node.js can outperform nginx in a lot of aspect.

All said I have to stay NginX has an in-built cache, whereas node.js doesn't come with it factory installed (YOU HAVE TO BUILD YOUR OWN FILE CACHE).
The custom file cache does outperform nginx and any other server in the market as it is super simple.

Also Nginx runs on multiple cores. To use the full potential of Node you have to cluster node servers. If you are interested to know how then please pm.

You need to deep digger to achieve performance nirvana with node, that is the only problem. Once done hell yeah... it beats Nginx.

blocks|key|606655|text|我对@gremo的图表有不同的解释。在我看来，在相同的请求数量(9-10k之间)下，它同时具有node和nginx规模。当然，nginx的响应延迟降低了20ms，但我认为用户不一定会察觉到这种差异(如果你的应用构建得很好)。给定固定数量的机器，在将节点机器转换为nginx之前，考虑到大多数负载将首先发生在节点机器上，将需要相当多的负载。与此对应的是，如果您已经将一台机器专用于nginx进行负载均衡。如果是这样的话，你也可以让它为你的静态内容提供服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|606656|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have a different interpretation of @gremo's charts. It looks to me like both node and nginx scale at the same number of requests (between 9-10k). Sure the latency in the response for nginx is lower by a constant 20ms, but I don't think users will necessarily perceive that difference (if your app is built well).
Given a fixed number of machines, it would take quite a significant amount of load before I would convert a node machine to nginx considering that node is where most of the load will occur in the first place.
The one counterpoint to this is if you are already dedicating a machine to nginx for load balancing. If that is the case then you might as well have it serve your static content as well.

Is there any benchmark or comparison which is faster: place nginx in front of node and let it serve static files directly or use just node and serve static files using it?

nginx solution seems to be more manageable for me, any thoughts?

node.js itself or nginx frontend for serving static files?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

有没有更快的基准测试或者比较:把nginx放在node前面，让它直接服务静态文件，或者只使用node，使用它服务静态文件？nginx解决方案对我来说似乎更容易管理，你有什么想法吗？

问node.js本身还是为静态文件提供服务的nginx前端？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问node.js本身还是为静态文件提供服务的nginx前端？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问node.js本身还是为静态文件提供服务的nginx前端？
EN