由网友(公子好风骨)分享简介：我做性能调优在SPARC硬件上运行我们Tomcat集群。 32位JVM给了我们足够的内存了，但我们要开始使用兵马俑服务器条纹因此额外的内存64位JVM提供可能需要很快。I'm doing performance tuning for our Tomcat cluster running on SPARC hardwa...

我做性能调优在SPARC硬件上运行我们Tomcat集群。 32位JVM给了我们足够的内存了，但我们要开始使用兵马俑服务器条纹因此额外的内存64位JVM提供可能需要很快。

I'm doing performance tuning for our Tomcat cluster running on SPARC hardware. The 32-bit JVM gives us sufficient memory for now, but we are going to start using Terracotta for server striping so the extra memory the 64-bit JVM offers could be needed soon.

在另外一个更大的内存占用，转移到对SPARC导致性能损失的64位JVM。这个FAQ显示了10％ - 20％的性能的64位JVM对SPARC 1.4的版本命中：

In addition to a bigger memory footprint, moving to the 64-bit JVM on SPARC results in a performance penalty. This FAQ shows a 10% - 20% performance hit for version 1.4 of the 64-bit JVM on SPARC:

http://java.sun.com/docs/hotspot/HotSpotFAQ。 HTML＃64bit_performance

我没兴趣参加一个10％ - 20％的性能损失，如果我能避免它。有使用32位/ 64位混合的方法来避免这个问题，所以也许在1.6 JVM不具备的性能已经讨论打到了1.4 JVM有：

I'm not interested in taking a 10% - 20% performance hit if I can avoid it. There's been discussion of using a 32-bit / 64-bit hybrid approach to avoid this problem so maybe the 1.6 JVM doesn't have the performance hit that the 1.4 JVM had:

的 http://blog.juma.me.uk/2008/10/14/32-bit-or-64-bit-jvm-how-about-a-hybrid/

有没有人有当前性能指标用在SPARC 1.6版本，从32位JVM迁移到64位JVM？

Does anyone have current performance metrics for moving from the 32-bit JVM to the 64-bit JVM using version 1.6 on SPARC?

感谢。

院长

推荐答案

下面是一些成果的基础上测试客户端调用了几个我们的Web服务使用64位和32位版本的JDK在Solaris上运行的Tomcat 5.5 1.6.0_13。

Here are some results based on test clients calling a couple of our web services running on Tomcat 5.5 on Solaris using the 64-bit and 32-bit versions of JDK 1.6.0_13.

64位JVM上的Tomcat 5.5使用默认设置时，产生了大约7％的性能损失。当我翻了一倍Tomcat的参数acceptCount和maxThreads至1000各性能影响的64位JVM小于1％。这可能是因为在1000线程对应并发测试客户我使用了试验的次数。

The 64-bit JVM resulted in a performance hit of about 7% when using the default settings on Tomcat 5.5. When I doubled the Tomcat parameters acceptCount and maxThreads to 1000 each the performance hit for the 64-bit JVM was less than 1%. This may be because the 1000 threads corresponded to the number of concurrent test clients I was using in the tests.

更改这些参数，降低了时间为32位和64位JVM，但64位JVM出现较大的性能提升。

Changing these parameters lowered the times for both 32-bit and 64-bit JVMs, but the 64-bit JVM showed a larger performance improvement.

您的里程可能会有所不同，但。

Your mileage may vary, though.