James Gosling blogs about Java software performance myths詹姆斯戈斯林博客关于Java软件的性能神话 and posts an interesting story (below).和员额的有趣的故事（见下文） 。 The comments contains few more stories from the trenches as they say.评论包含数更多的故事，从战壕正如他们所说。 Lets look at the real picture shall we?让看看真正的图片我们应？

There was a funny incident at a recent developer event where some folks had a booth where they where demo-ing a high end industrial strength C compiler and had a benchmark that they had transliterated into Java.有一个有趣的事件在最近一次开发活动的一些乡亲有一个摊位，他们那里演示-荷兰高端工业实力的C编译器和一个基准，他们译音到爪哇。 They were comparing their compiler to GCC and Java.他们比较他们的编译器，海湾合作委员会和Java 。 GCC was running at about 2/3 the performance of this high end compiler; the Java version was running at about 2/3 the performance of the GCC version.海湾合作委员会是运行在约2 / 3的表现，这高端编译器; Java版本是运行在约2 / 3的表现，海湾合作委员会的版本。 Folks were gathered around the booth and someone noticed that the script they were using to run the Java version didn’t have optimisation turned on.乡亲聚集周围的摊位，有人注意到，该脚本，他们使用运行Java版没有优化打开。 A few seconds with vi to add the “-server” switch and Java’s performance jumped up to match the fancy C compiler.几秒钟后，与六，添加“服务器”开关和Java的表现，跳跃，以配合花式C编译。 This got the pro-GCC crowd all excited, so a bunch of them started fiddling with its command line switches.这得到了亲，海湾合作委员会的所有人群兴奋，所以一群，他们开始fiddling其命令行开关。 They got a bit of improvement, but not much (the original selection had been pretty good).他们得到了一点改善，但没有太大的（原来的选择已经相当不错） 。

Author: James Gosling from Sun作者：詹姆斯戈斯林从Sun

In 2001 when I was working at AltaVista I started a push to move us to using Java at the front end.在2001年，当我在工作altavista我开始推动动议，我们使用Java在前端。 At the time an executive had stated that Java was 40 times slower than C, and that it was easy to proove.在当时的一个行政曾表示， Java的是40倍，比C慢，而且它是很容易proove 。 So he sent me 4 programs he had written 4 years previously (when Java really was slow).因此，他寄给我的四程序，他曾致函四年以前（当Java的真的是缓慢） 。 I had a look at them, optimised the IO a little (there was no buffering) and the result was that the java programs were only at most 10% slower than the C program (one of them was actually faster) But of course the Java program did a lot more: for one it was completely unicode enabled, whereas the c program was not.我看看他们，优化团一点（有没有缓冲）和其结果是，该Java程序，只有在最慢的10 ％ ，比C程序（其中一人，实际上是更快） ，但当然的Java计划做了大量更多：一，它是完全的Unicode启用，而C程序没有。 And that was before NIO.这是之前的NiO 。

Soon after this AltaVista moved to rewriting all of its front end in java.后不久，这altavista转移到重写其所有的前端，在Java语言。 I left to do other things, but was told that it was a great success.我离开，以做其他事情，但被告知，这是一个巨大的成功。 (Now if only they had listened to me 5 years previously when I told the CEO that they were not making the best of the resource hidden inside hyperlinks…) （现在，如果只有他们听取了我五年以前当我告诉行政总裁，他们没有作出最好的资源藏有超连结… … ）

Author: Henry Story from BblFish作者：亨利的故事，从bblfish

In yet another situation I was in, the company was prototyping in C++ because of concerns with performance.但在另一种情况，我在，该公司的原型在C + + ，因为担心与表现。 They were worried about performance in an application that was never going to see production and in the meantime spend a lot more time producing it.他们担心表现在应用程序，这是永远不会看到，生产和在此期间花费大量的时间生产。 When questioned further one could find no basis for their concerns.当被问及进一步之一，能找到就没有了基础，他们的忧虑。 They could not find one spot in the architecture where performance was so critical that it required the use of C++.他们无法找到一个位置，在那里建筑的表现是如此重要，它需要使用的C + + 。 Even in the face of this evidence and analysis the myth was so strong for them that they were unable to see the reality of the situation.即使在面对这个证据和分析神话是如此强大，为他们，他们没能看到现实的情况。

Author: Kirk from Java Performance Tuning作者：柯克从Java性能调优

Personally I have found in bioinformatics world (high throughput distributed processing like genomic annotations) Java software performance competes favorably with C. Will the rumor mongers now finally put a stop to this “java performance issues” BS?我个人发现，在世界生物信息学（高吞吐量分布式处理一样，基因组的注释）的Java软件性能的良性竞争与长会的传闻mongers现在终于提出了制止这种“ Java性能问题”的布呢？