您是如何根据规范的结果来分析xeon和超声波的？
您是如何根据规范的结果来分析xeon和超声波的？
提问于 2013-08-15 13:50:32
我正在尝试对xeon处理器和超小型IV+进行比较。
对于xeon，我有这样的结果：
思科UCS B200M3英特尔Xeon处理器E5-2660 (桑迪桥)
Hardware Vendor System Result Baseline # Cores # Chips # Cores Per Chip Published Disclosure
Bull SAS NovaScale R440 F3 (Intel Xeon E5-2660, 2.20 GHz) 47.6 44.5 16 2 8 Apr-2012 HTML CSV PDF PS Text Config
Bull SAS NovaScale R460 F3 (Intel Xeon E5-2660, 2.20 GHz) 47.7 44.5 16 2 8 Apr-2012 HTML CSV PDF PS Text Config
Bull SAS NovaScale T840 F3 (Intel Xeon E5-2660, 2.20 GHz) 47.4 44.3 16 2 8 Mar-2012 HTML CSV PDF PS Text Config
Cisco Systems Cisco UCS C220 M3 (Intel Xeon E5-2660, 2.20 GHz) 48.3 45.0 16 2 8 Jul-2012 HTML CSV PDF PS Text Config
Cisco Systems Cisco UCS C240 M3 (Intel Xeon E5-2660, 2.20 GHz) 48.5 45.2 16 2 8 Jul-2012 HTML CSV PDF PS Text Config 对于超声IV来说，
Model Processor Type Processor CPU Cores No of Processors Memory
SUN FIRE V490 SUN ULTRASPARC IV+ 1500 8.00 4.00 32768硬件供应商系统结果基线#核#芯片#芯片每片公布太阳微系统太阳火V490 78.0 71.7 8 4 2 2007年4月2日HTML文本Config
看看这些结果，哪个结果表现得更好，如何读取这个输出？
这是规格输出: Intel Xeon处理器E7-4860。
Benchmark Base # Copies Base Run Time Base Rate Base Selected Base Status Peak # Copies Peak Run Time Peak Rate Peak Selected Peak Status Description
400.perlbench 80 988.746037 790.49624 1 S 80 827.236707 944.83232 1 S SelectedIteration (base #3; peak #2)
401.bzip2 80 1401.357446 550.8944 1 S 80 1329.663649 580.59792 1 S SelectedIteration (base #3; peak #1)
403.gcc 80 821.134215 784.28104 1 S 80 818.863431 786.45592 1 S SelectedIteration (base #1; peak #1)
429.mcf 80 627.881517 1162.00264 1 S 80 596.869458 1222.37784 1 S SelectedIteration (base #3; peak #3)
445.gobmk 80 929.814428 902.54568 1 S 80 883.392809 949.97376 1 S SelectedIteration (base #1; peak #3)
456.hmmer 80 606.72107 1230.21936 1 S 80 481.870461 1548.964 1 S SelectedIteration (base #3; peak #1)
458.sjeng 80 1111.901674 870.58056 1 S 80 1040.358199 930.4488 1 S SelectedIteration (base #2; peak #2)
462.libquantum 80 366.940844 4517.34936 1 S 80 366.940844 4517.34936 1 S SelectedIteration (base #2; peak #2)
464.h264ref 80 1437.900502 1231.2396 1 S 80 1444.884847 1225.28792 1 S SelectedIteration (base #1; peak #1)
471.omnetpp 80 900.233245 555.4116 1 S 80 840.44434 594.92336 1 S SelectedIteration (base #2; peak #1)
473.astar 80 974.344331 576.3876 1 S 80 974.344331 576.3876 1 S SelectedIteration (base #3; peak #3)
483.xalancbmk 80 575.587683 959.01984 1 S 80 575.587683 959.01984 1 S SelectedIteration (base #1; peak #1)
Intel Xeon Processor E5-2660 (Sandy Bridge)
Benchmark Base Ref Time Base Run Time Base Ratio Base Selected Base Status Peak Ref Time Peak Run Time Peak Ratio Peak Selected Peak Status Description
400.perlbench 9770 363.71793 26.861475 1 S 9770 308.821887 31.636359 1 S SelectedIteration (base #1; peak #3)
401.bzip2 9650 481.936537 20.023383 1 S 9650 473.177143 20.394054 1 S SelectedIteration (base #2; peak #2)
403.gcc 8050 275.243939 29.246784 1 S 8050 273.476945 29.435754 1 S SelectedIteration (base #1; peak #2)
429.mcf 9120 152.092584 59.963476 1 S 9120 152.092584 59.963476 1 S SelectedIteration (base #3; peak #3)
445.gobmk 10490 492.109626 21.316389 1 S 10490 455.186823 23.045483 1 S SelectedIteration (base #3; peak #2)
456.hmmer 9330 202.295578 46.120632 1 S 9330 197.804691 47.167739 1 S SelectedIteration (base #3; peak #3)
458.sjeng 12100 484.218283 24.98873 1 S 12100 486.068138 24.893629 1 S SelectedIteration (base #2; peak #2)
462.libquantum 20720 8.110392 2554.747046 1 S 20720 8.110392 2554.747046 1 S SelectedIteration (base #2; peak #2)
464.h264ref 22130 567.298128 39.009471 1 S 22130 463.737891 47.720923 1 S SelectedIteration (base #3; peak #3)
471.omnetpp 6250 252.260035 24.776021 1 S 6250 185.447273 33.702302 1 S SelectedIteration (base #1; peak #2)
473.astar 7020 262.741702 26.718256 1 S 7020 262.741702 26.718256 1 S SelectedIteration (base #3; peak #3)
483.xalancbmk 6900 151.761465 45.466087 1 S 6900 144.520671 47.744035 1 S SelectedIteration (base #2; peak #3)
SUN FIRE V490 SUN ULTRASPARC IV+
Benchmark Base # Copies Base Run Time Base Rate Base Selected Base Status Peak # Copies Peak Run Time Peak Rate Peak Selected Peak Status Description
400.perlbench 8 1224.828996 63.81298961 1 S 8 891.155322 87.7063718 1 S SelectedIteration (base #2; peak #3)
401.bzip2 8 1580.039751 48.85953024 1 S 8 1318.300807 58.56023116 1 S SelectedIteration (base #1; peak #3)
403.gcc 8 1186.319051 54.28556504 1 S 8 1118.707572 57.56642899 1 S SelectedIteration (base #2; peak #2)
429.mcf 8 715.023723 102.0385725 1 S 8 714.701975 102.0845087 1 S SelectedIteration (base #3; peak #2)
445.gobmk 8 1181.380568 71.03553442 1 S 8 1001.299034 83.8111265 1 S SelectedIteration (base #1; peak #3)
456.hmmer 8 1061.728244 70.30047512 1 S 8 1055.574115 70.71033567 1 S SelectedIteration (base #3; peak #1)
458.sjeng 8 1527.577971 63.36828747 1 S 8 1415.486478 68.38638271 1 S SelectedIteration (base #1; peak #1)
462.libquantum 8 1289.56188 128.5397797 1 S 8 1278.533905 129.6484977 1 S SelectedIteration (base #2; peak #1)
464.h264ref 8 1757.491311 100.7344952 1 S 8 1543.499756 114.7003745 1 S SelectedIteration (base #1; peak #2)
471.omnetpp 8 1007.226126 49.64128581 1 S 8 947.26431 52.78357843 1 S SelectedIteration (base #2; peak #3)
473.astar 8 871.046418 64.47417593 1 S 8 871.046418 64.47417593 1 S SelectedIteration (base #2; peak #2)
483.xalancbmk 8 677.614178 81.46228605 1 S 8 677.614178 81.46228605 1 S SelectedIteration (base #3; peak #3) 回答 2
Server Fault用户
发布于 2013-08-15 14:12:43
这不是一个简单的问题，不同的芯片在不同的任务上会做得更好。通常，对于温和的使用，纯计算英特尔将得到更好的价格/性能，但Sparc可以超过它，特别是在高端多线程进程，需要高并发/低延迟。
如果你不知道你需要，否则，你可能想坚持英特尔，在你开始研究奇异的硬件(好，太阳不是完全异国情调.)你需要找出你的瓶颈所在。如果您的带宽和延迟受限于您的存储子系统，那么世界上所有的处理能力都不会使您跑得更快。
Server Fault用户
发布于 2013-08-15 15:03:07
了解这将如何影响应用程序的唯一方法是在不同平台上对应用程序进行实际基准测试。反正你也不会运行同样的二进制文件。为Intel arch重新编译应用程序，并在工作站上运行它以获得一些性能数字。然后将工作站与某些服务器规范进行比较。
页面原文内容由Server Fault提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://serverfault.com/questions/531243
复制相关文章
相似问题
腾讯云开发者
Copyright © 2013 - 2026 Tencent Cloud. All Rights Reserved. 腾讯云 版权所有
深圳市腾讯计算机系统有限公司 ICP备案/许可证号：粤B2-20090059 
粤公网安备44030502008569号
腾讯云计算（北京）有限责任公司 京ICP证150476号 | 京ICP备11018762号