blocks|key|728186|text|不是的。在性能方面，没有人能胜过一个专家写的(例如，Node.js)的实现，他花了一年的时间在汇编程序中实现它，专注于针对特定体系结构和特定数据文件的性能(由基准测试和计时信息支持，在发布版本中被删除)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|728187|当然，瓶颈是下载程序，而不是实际的运行时性能，然而，考虑到它的大小，手工制作的汇编程序仍然很难被击败。|728188|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|$]]

No. Nobody can beat, performance wise, an implementation of (eg, Node.js) written by an expert who has spent a year implementing it in assembler, with a focus on performance (backed by benchmarks and timing information, which is removed in a release version), for a particular architecture and particular data file.

Of course, the bottleneck is downloading the program, not in the actual runtime performance, however, hand-crafted assembler would still be very hard to beat given its size.

blocks|key|724819|text|Yes,+according+to+the+Computer+Language+Benchmarks+game，但是be+careful+interpreting+results+from+artificial+benchmarks.|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|724820|默认比较是与Java进行比较，Java通常更快，但您可以将其与Perl、PHP以及几个Ruby和Python实现进行比较。除了在使用大整数的基准测试中，它似乎更快，因为JavaScript本身并不支持它们。|724821|entityMap|0|LINK|mutability|MUTABLE|url|http://shootout.alioth.debian.org/u32/benchmark.php?test=all&lang=v8|1|http://shootout.alioth.debian.org/dont-jump-to-conclusions.php^0|0|1J|0|1M|1M|1|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

<a href="http://shootout.alioth.debian.org/u32/benchmark.php?test=all&amp;lang=v8" rel="nofollow">Yes, according to the Computer Language Benchmarks game</a>, but <a href="http://shootout.alioth.debian.org/dont-jump-to-conclusions.php" rel="nofollow">be careful interpreting results from artificial benchmarks</a>.

The default comparison is to Java, which is generally faster, but you can compare it to Perl, PHP and several Ruby and Python implementations. It seems to be mostly faster except in the benchmarks that use big integers, because JavaScript doesn't support them natively.

blocks|key|1446465|text|这取决于应用程序。在相同的特定情况下，从长远来看，它比GCC/C%2B%2B更快。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1446466|http://wingolog.org/archives/2011/06/10/v8-is-faster-than-gcc|offset|length|1446467|​|1446468|📷|atomic|1446469|1446470|1446471|说得对，V8总是比GCC快，直到它的固定数开始失效。根据记录，只有图表右侧的点才真正有价值，因为左侧的点只运行几毫秒。|blockquote|1446472|1446473|AdamK说：|1446474|看起来合乎逻辑。GCC只处理一次代码，做完之后就没有改进的余地了。V8一遍又一遍地处理相同的代码，并且可以随着时间的推移改进优化。|1446475|通常情况下，您只需要使用GCC编译一次代码。没有人会在每次想要使用什么东西的时候编译所有的东西。因此，比较V8和GCC的compile%2Brun时间是不公平的--要创建好的代码，GCC的工作要难得多，因为它不能随着时间的推移而改进。|1446476|entityMap|0|LINK|mutability|MUTABLE|url|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/0b51854b1f3acb4c58b1968d58deedc5.png|imageAlt^0|0|0|1P|0|0|0|0|1|1|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@]|9|@$D|1B|E|1C|1|1D]]|A|$]]|$1|F|3|G|5|6|7|1E|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1F|8|@]|9|@$D|1G|E|1H|1|1I]]|A|$]]|$1|K|3|G|5|6|7|1J|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|1L|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1N|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1O|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1P|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|C]]|13|$5|14|10|15|A|$16|17|18|-4]]]]

It depends of the application. In same specific cases it's faster than GCC/C++ in the long run.

<a href="http://wingolog.org/archives/2011/06/10/v8-is-faster-than-gcc" rel="nofollow noreferrer">http://wingolog.org/archives/2011/06/10/v8-is-faster-than-gcc</a>

<img src="https://i.stack.imgur.com/lJDcX.png" alt="enter image description here">

<blockquote>
 That's right, V8 is always faster than GCC, right up to the point at which its fixnums start failing. For the record, only the points on the right of the graph are really worth anything, as the ones on the left only run for a few milliseconds.
 
 AdamK says:
 
 Seems logical. GCC deals with the code only once, ant after it's done there is no room for improvement. V8 deals with the same code over and over and can improve optimization over time.
 
 You usually compile code with GCC only once. Noone compiles everything everytime he wants to use something. So, comparing compile+run time between V8 and GCC is not fair - GCC has much harder job to do to create good code, because it can't improve it over time.
</blockquote>

Anyone know whether Javascript on V8 runs faster than equivalent code on other languages such as Python, Perl, PHP etc...?

Is Javascript under V8 faster than equivalent code on other languages?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

有人知道V8上的Javascript是否比其他语言上的同等代码运行得更快吗？

问在V8下的Javascript比在其他语言上的同等代码快吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在V8下的Javascript比在其他语言上的同等代码快吗？EN