1、如何選擇Linux服務器替換UNIXIR Hsieh，資深架構師朱明，架構師2本演講根據系統性能比較與硬件可靠性來介紹如何選擇VMware-Linux服務器來替換如 PowerVM-AIX 之類的UNIX 服務器。1. 用戶對PowerVM-AIX 與 VMware-Linux性能的傳統看法2. PowerVM-AIX 與 VMware-Linux實際的性能比較3. VMware-Linux為何性能與PowerVM-AIX不相上下4. 結語 顛覆傳統 - 31. 用戶對PowerVM-AIX 與 VMware-Linux性能的傳統看法2. PowerVM-AIX 與 VMware-Linux實

2、際的性能比較3. VMware-Linux為何性能與PowerVM-AIX不相上下4. 結語 顛覆傳統 - PowerVM-AIX 與 VMware-Linux性能比（一個核與一個核的性能比較）2008年以前 ： 3.5 比 12012 天才ISV測試報告 30 比 12013傳說年某大國企集采用 4 比 14電不夠用，拿掉一臺 PowerVM-AIX機可以抵三臺AIX-PowerVM 的其他難題 ：耗電5某大型商業銀行新一代應用測試結果江蘇某銀行6Vmware+x86 與 PowerVM+AIX國內最大的電子銀行系統應用性能的比較測試環境的比較測試結果資源使用的比較測試結果響應時間的比較7*

3、RPERF : RPERF calculated by Stephen ChuVMwareIBM X3650（12核）PowerVMIBM PowerLinux 7R2（16核）81. 用戶對PowerVM-AIX 與 VMware-Linux性能的傳統看法2. PowerVM-AIX 與 VMware-Linux實際的性能比較3. VMware-Linux為何性能與PowerVM-AIX不相上下4. 結語 顛覆傳統 - 9超級電腦排名 2013/0612/31/202191. 天河(Tianhe) 2 Intel Xeon+Phi 2. 泰坦(Titan) AMD+Nvidia K20 x

4、3. 紅杉(Sequoia) IBM Power 4. 京(K) Fujitsu SPARC 64 10Intel Xeon Processor E7 Family SPARC* T4-4POWER 750Express*Up to2XPerformanceUp to1.12XPerformanceat19%Price/Performanceat19%System Cost 4-SocketIntel XeonE7-88374-SocketIntel XeonE7-4870Intel Xeon E7 vs. SPARC*Intel Xeon E7 vs. Power*112-socket4-s

5、ocket8-socketIntel Xeon Processor E7 系列Xeon CPU SocketMemoryI/O HubIntel QuickPath Interconnect3rd partry Node Controller(non-Intel)OEM interconnect.1 Additional Configurations via OEM-specific scaling technologies (up to 256-sockets)8S1(3rd party node controller)支持 2S, 4S, 8S, 12什么因素決定主機性能？CPU處理時間內

6、存處理時間I/O處理時間計算資源處理時間I/O處理時間處理器、內存、I/O處理時間會因不同的應用程序和不同類型的主機有非常大的差異 單臺主機性能由以下因素決定:除了CPU處理能力外，還有更多的因素需要考慮13IBM 大機的大機的“ “中斷中斷” ”(Interrrupt)種類種類Supervisor calls or SVC interrupts - These interrupts occur when the program issues an SVC to request a particular system service. An SVC interrupts the program

7、 being executed and passes control to the supervisor so that it can perform the service. Programs request these services through macros such as OPEN (open a file), GETMAIN (obtain storage), or WTO (write a message to the system operator). I/O interrupts - These interrupts occur when the channel subs

8、ystem signals a change of status, such as an input/output (I/O) operation completing, an error occurring, or an I/O device such as a printer has become ready for work. External interrupts - These interrupts can indicate any of several events, such as a time interval expiring, the operator pressing t

9、he interrupt key on the console, or the processor receiving a signal from another processor. Restart interrupts - These interrupts occur when the operator selects the restart function at the console or when a restart SIGP (signal processor) instruction is received from another processor. Program int

10、errupts - These interrupts are caused by program errors (for example, the program attempts to perform an invalid operation), page faults (the program references a page that is not in central storage), or requests to monitor an event. Machine check interrupts - These interrupts are caused by machine

11、malfunctions.14數據敏感型的負載，例如大型數據庫、 在線交易、 面向對象編碼（Object Oriented code）和上下文切換（context switching）此類應用可能在IBM的z系列服務器上運行得更好CPU處理時間內存處理時間I/O處理時間處理時間CPU處理時間內存處理時間I/O處理時間處理時間zSeriesRISC & x86決定主機性能的因素 I/O密集型除了CPU處理能力外，還有更多的因素需要考慮15CPU處理時間內存處理時間I/O處理時間處理時間zSeries處理時間RISC & x86CPU敏感型負載，例如SPECint, Deep Co

12、mputing, 渲染(Graphic Rendering) 等在IBM z系列服務器上表現則很糟糕不需要CPU、內存和I/O處理能力整體均衡，只依賴CPU處理能力的負載在x86架構平臺上會表現更好除了CPU處理能力外，還有更多的因素需要考慮CPU處理時間內存處理時間I/O處理時間決定主機性能的因素 計算密集型16前端總線(Front-Side-Bus)17前端總線FSB VS. QPI快速通道互聯1818Quick Path Interconnect快速通道互快速通道互聯聯1920下面哪一種更有價值？*桌面電腦服務器關鍵業務服務器*系統崩潰：幾乎每周一次藍屏：幾乎每月一次平均無故障時間：30

13、天系統崩潰：幾乎沒有藍屏：有狀態記錄，可分析故障根源平均無故障時間：1年系統崩潰：沒有藍屏：使用容錯技術避免平均無故障時間：5年RAS（Reliability、Availability、Serviceability）與價值成正比* 假設計算能力相同21穩定性系統可以檢測錯誤、標記并糾正錯誤使用FIT(Failure in Time故障時間)衡量一次FIT = 一次故障 / 十億小時 (平均無故障時間=11萬4千年!)可用性系統即使在出現故障的情況下依然可以保持正常運作使用周期內(通常為一年)的停機時間來衡量五個九99999 (99.999% 可用時間) = 只允許每月22秒的停機時間可服務性系

14、統可以報告故障并便于修復 (衡量標準：MTTR，平均修復時間)RAS 穩定性、可用性、可服務性22人為失誤 邏輯錯誤 (bugs), 誤操作等硬故障風扇、電源、主板電容等故障硬盤或陣列卡故障內存模組故障軟故障軟故障主要來源于Alpha particles and neutrons*軟故障無可避免并且逐漸變成“主導因素”1.半導體製程收縮2.工作電壓降低3.電晶體數量增加2影響RAS的因素* 參考資料: J.F. Ziegler, Terrestrial cosmic rays, IBM Journal of Research and Development, Vol. 40, no. 1, p

15、p. 19-40, Jan 1996Memory23固態電容242425冗余的風扇帶ECC功能的內存模組& DDDC & 內存鏡像 X86架構服務器部件冗余的電源263380/3390 薄膜讀寫頭9340/9345 MR磁阻讀寫頭大型機專用硬件？27 Cisco UCS B440 Intel Nehalem EX處理器 CPU 192個核心 CPU利用率10% 操作系統 Red Hat Linux / vSphere* 存儲 Symmetrix VMAX Sun Fire E25K UltraSPARC IV處理器 CPU 224個核心 CPU利用率80% 操作系統 Solar

16、is 10 存儲 Symmetrix DMX-3Unified Comm. SystemSun Fire Server* In Progress 28IBM 大機的大機的“ “中斷中斷” ”(Interrrupt)種類種類Supervisor calls or SVC interrupts - These interrupts occur when the program issues an SVC to request a particular system service. An SVC interrupts the program being executed and passes co

17、ntrol to the supervisor so that it can perform the service. Programs request these services through macros such as OPEN (open a file), GETMAIN (obtain storage), or WTO (write a message to the system operator). I/O interrupts - These interrupts occur when the channel subsystem signals a change of sta

18、tus, such as an input/output (I/O) operation completing, an error occurring, or an I/O device such as a printer has become ready for work. External interrupts - These interrupts can indicate any of several events, such as a time interval expiring, the operator pressing the interrupt key on the conso

19、le, or the processor receiving a signal from another processor. Restart interrupts - These interrupts occur when the operator selects the restart function at the console or when a restart SIGP (signal processor) instruction is received from another processor. Program interrupts - These interrupts ar

20、e caused by program errors (for example, the program attempts to perform an invalid operation), page faults (the program references a page that is not in central storage), or requests to monitor an event. Machine check interrupts - These interrupts are caused by machine malfunctions.29MCA Machine Ch

21、eck Architecture檢測CPU、內存與I/O錯誤與操作系統協同修復錯誤從非核心系統錯誤中恢復30硬件不可糾正錯誤帶有錯誤預防機制的設備正常運行錯誤由軟件修復錯誤被修復發現錯誤*保留錯誤內容硬件可糾正錯誤硬件不可糾正錯誤通過OS、VMM或DBMS等組件協同工作，修復或重啟進程使其恢復正常運作帶錯誤的內存區域被標記使其中數據不會被系統或應用程序調用錯誤信息傳遞到軟件層面MCA Recovery*使用輪詢檢測或精確緩存回寫技術檢測錯誤Machine Check Architecture Recovery使系統從非核心錯誤中修復31O SVMMDBMS不可由硬件修復的錯誤將被OS隔離并由O

22、S進行修復*受影響的應用程序有可能需要重新啟動恢復系統依然保持運作不受影響Window Server*2008 R2 +RHEL* 6 +U8+SLES11* SP1 +不可由硬件修復的錯誤將在DBMS（數據庫管理服務）緩沖池中被隔離*受影響的非關鍵緩沖在磁盤中重新讀取系統和DBMS保持運作不受影響HANA IMDB 1.0 SP3+* Other names and brands may be claimed as the property of othersvSphere* 5.0+RHEL* 6 + - KVMSLES11* SP1 +Window Server* Hyper-VMicrosoft SQL-Server 2012不可由硬件修復的錯誤將被VMM隔離至單個虛擬機內*受影響的虛擬機有可能需要重新啟動恢復Hypervisor和其他虛擬機依然正常工作不受影響Machine Check Architecture Recovery軟件業界不斷增加支持可擴展的錯誤恢復架構*使