In theory, for long running server-type application, a JIT-compiled language can become much faster than a natively compiled counterpart. Since the JIT compiled language is generally first compiled to a fairly low-level intermediate language, you can do a lot of the high-level optimizations right at compile time anyway. The big advantage comes in that the JIT can continue to recompile sections of code on the fly as it gets more and more data on how the application is being used. It can arrange the most common code-paths to allow branch prediction to succeed as often as possible. It can re-arrange separate code blocks that are often called together to keep them both in the cache. It can spend more effort optimizing inner loops.

我怀疑。net或任何jre都能做到这一点，但早在我上大学的时候就有人在研究这一点，所以认为这类东西很快就会在现实世界中找到自己的方式也不是不合理的。

我发现2020年4月读过:https://www.quora.com/Why-is-C-so-slow-compared-to-Python，作者是一位拥有15年以上软件开发经验的现实世界的程序员。

它指出，c#通常较慢，因为它被编译为公共中间语言(CIL)，而不是像c++那样的机器代码。然后，CIL通过公共语言运行库(CLR)输出机器代码。但是，如果您继续执行c#，它将获取机器代码的输出并缓存它，以便为下次执行保存机器代码。总而言之，如果多次执行，c#会更快，因为它是多次执行后的机器代码。

也有评论说，一个优秀的c++程序员可以做一些耗时的优化，但最终会被优化。

C/ c++在有大型数组或数组(任何大小)上的大量循环/迭代的程序中可以表现得更好。这就是为什么在C/ c++中图形化通常要快得多，因为几乎所有的图形化操作都基于繁重的数组操作。net在数组索引操作中是出了名的慢，这是由于所有的安全检查，这对于多维数组尤其如此(是的，矩形c#数组甚至比锯齿形c#数组还要慢)。

The bonuses of C/C++ are most pronounced if you stick directly with pointers and avoid Boost, std::vector and other high-level containers, as well as inline every small function possible. Use old-school arrays whenever possible. Yes, you will need more lines of code to accomplish the same thing you did in Java or C# as you avoid high-level containers. If you need a dynamically sized array, you will just need to remember to pair your new T[] with a corresponding delete[] statement (or use std::unique_ptr)—the price for the extra speed is that you must code more carefully. But in exchange, you get to rid yourself of the overhead of managed memory / garbage collector, which can easily be 20% or more of the execution time of heavily object-oriented programs in both Java and .NET, as well as those massive managed memory array indexing costs. C++ apps can also benefit from some nifty compiler switches in certain specific cases.

I am an expert programmer in C, C++, Java, and C#. I recently had the rare occasion to implement the exact same algorithmic program in the latter 3 languages. The program had a lot of math and multi-dimensional array operations. I heavily optimized this in all 3 languages. The results were typical of what I normally see in less rigorous comparisons: Java was about 1.3x faster than C# (most JVMs are more optimized than the CLR), and the C++ raw pointer version came in about 2.1x faster than C#. Note that the C# program only used safe code—it is my opinion that you might as well code it in C++ before using the unsafe keyword.

Lest anyone think I have something against C#, I will close by saying that C# is probably my favorite language. It is the most logical, intuitive and rapid development language I've encountered so far. I do all my prototyping in C#. The C# language has many small, subtle advantages over Java (yes, I know Microsoft had the chance to fix many of Java's shortcomings by entering the game late and arguably copying Java). Toast to Java's Calendar class anyone? If Microsoft ever spends real effort to optimize the CLR and the .NET JITter, C# could seriously take over. I'm honestly surprised they haven't already—they did so many things right in the C# language, why not follow it up with heavy-hitting compiler optimizations? Maybe if we all beg.

根据我的经验(这两种语言我都用过很多)，与c++相比，c#的主要问题是内存消耗高，而且我还没有找到控制它的好方法。最终导致。net软件变慢的是内存消耗。

另一个因素是JIT编译器不能提供太多时间来进行高级优化，因为它在运行时运行，如果花费太多时间，最终用户会注意到它。另一方面，c++编译器有足够的时间在编译时进行优化。恕我直言，这个因素远没有内存消耗那么重要。

我知道这不是你想问的，但是c#通常比c++写得更快，这在商业环境中是一个很大的好处。

垃圾收集是Java#不能用于实时系统的主要原因。

GC什么时候会发生? 需要多长时间?

这是不确定的。