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性能問題”的布呢？