規劃 Service Manager 硬體效能Plan for Service Manager hardware performance

重要

此版本的 Service Manager 已達到終止支援,建議您 升級至 Service Manager 2019This version of Service Manager has reached the end of support, we recommend you to upgrade to Service Manager 2019.

System Center-Service Manager 效能的重要部分取決於硬體設定和部署拓撲,並規劃來處理貴組織的需求。An important part of System Center - Service Manager performance depends on a hardware configuration and deployment topology that is planned to handle the needs of your organization. 以下各節提供在規劃適當硬體效能時所需考量的一般原則。The following sections provide general guidelines to consider when you are planning for adequate hardware performance.

硬體效能Hardware performance

以下是 Service Manager 中最顯著的硬體瓶頸,Service Manager 資料庫中有大量的負載和資料量:The following are the hardware bottlenecks that are most noticeable in Service Manager, with a significant load and amount of data in the Service Manager database:

  1. 最常見的瓶頸是執行 Microsoft SQL Server 的電腦上的記憶體和 I/O。The most common bottleneck is memory and I/O on the computer that is running Microsoft SQL Server. 如果您有足夠的資源,請配置更多記憶體和更快的 IO 子系統來改善 SQL Server I/O,以達到更佳的效能。If you have the resources, investing in more memory and a faster I/O subsystem to improve SQL Server I/O will achieve better performance.
  2. 如果您預期有許多主控台連接到管理伺服器,您可以為管理伺服器投資額外的 Cpu 和記憶體,或安裝次要 Service Manager 管理伺服器,藉此改善效能以處理尖峰負載。If you expect to have many consoles connecting to a management server, you can improve performance to handle peak load by investing in additional CPUs and memory for the management server or by installing a secondary Service Manager management server.

請注意本文中針對每個角色所建議的最低硬體需求。Be aware of the recommended minimum hardware for each role, as described in this document.

虛擬機器的角色The role of virtual machines

許多組織使用虛擬機器來裝載 Windows Server 應用程式。Many organizations use virtual machines to host Windows Server applications. Service Manager 伺服器角色(例如管理伺服器和資料倉儲伺服器)都沒有例外。Service Manager server roles, such as the management server and data warehouse server, are no exceptions. 虛擬機器的使用範圍可能包含虛擬化所有的伺服器角色,或者是一些虛擬和實體電腦的組合。The use of virtual machines might range from all server roles being virtualized to some other combination of virtual and physical computers.

我們不建議任何特定的虛擬 - 到 - 實體 - 電腦比例,因為貴組織的需求本質上是唯一的。We do not recommend any specific virtual-to-physical-computer ratio because the needs of your organization are inherently unique. 不過,每個軟體角色的最低硬體需求皆可套用至實體電腦上。However, the minimum hardware requirements for each software role apply to physical computers. 如果您決定虛擬化軟體角色,應確定每部虛擬電腦皆具有額外的硬體資源。If you decide to virtualize a software role, you should plan to ensure that you have additional hardware resources for each virtual computer.

如果未遵照下列規劃指示,則資料庫伺服器可能會因為虛擬電腦的效能過低而受到損害:Database servers are vulnerable to poor performance on virtual machines if the following planning guidance is not followed:

  • 在超 - SQL Server 中執行V 環境Running SQL Server in a Hyper-V Environment.
  • 切勿在準備裝載 SQL Server 的虛擬機器上使用動態磁碟。You should never use dynamic disks on virtual machines that are intended to host SQL Server. 使用固定 - 大小的虛擬硬碟或傳遞 - 。Use fixed-size virtual hard drives or pass-through.
  • Hyper-v - 針對每個來賓僅允許四個虛擬 cpu,如果您有許多主控台,這可能會限制 Service Manager 的伺服器。Hyper-V allows only four virtual CPUs per guest, which might constrain the Service Manager server if you have many consoles.

Service Manager 基準測試結果Service Manager baseline test results

Service Manager 已 - 使用各種部署案例來測試效能和擴充性的基準,並以實體電腦的形式提供最低的建議硬體。Service Manager has been baseline-tested for performance and scalability using various deployment scenarios with the minimum recommended hardware in the form of physical computers. 更具體來說,這些案例已經過預先填入的資料庫進行測試,並 Service Manager 主控台在迴圈中建立及更新事件和變更要求。More specifically, the scenarios were tested with databases prepopulated and Service Manager consoles creating and updating Incidents and Change Requests in a loop.

此資料庫已預先填入兩種測試的資訊:The database was prepopulated with information for two tests:

  • 測試 1 包含 20,000 部電腦、20,000 名使用者和所有必要的設定項目,同時在資料庫中總計會有約 250 萬列的 250,000 個設定項目。Test 1 consisted of 20,000 computers, 20,000 users, and all the necessary configuration items, which were approximately 250,000 configuration items totaling approximately 2.5 million rows in the database. 測試1也包含 40 active Service Manager 主控台。Test 1 also included 40 active Service Manager consoles.
  • 測試 2 包含 50,000 部電腦、50,000 名使用者和所有相關的設定項目,同時在資料庫中總計會有約 600 萬列的 700,000 個設定項目。Test 2 consisted of 50,000 computers, 50,000 users, and related configuration items, which was approximately 700,000 configuration items totaling 6 million rows in the database. 測試2也包含 80 active Service Manager 主控台。Test 2 also included 80 active Service Manager consoles.

測試產生下列結果:The tests delivered the following results:

  • 為了符合50000電腦設定的回應 - 時間目標 - ,SQL Server 的記憶體必須從 8 gb ( gb 增加 ) 至 32 gb。To meet the response-time goals for the 50,000-computer configuration, the SQL Server memory had to be increased from 8 gigabytes (GB) to 32 GB.
  • 在測試期間,每小時都會產生20000電腦設定和500事件的200事件和50變更要求, - 以及針對 - 每個事件和變更要求處理三至四個通知訂閱和範本的125變更要求。During testing, 200 incidents and 50 change requests for the 20,000-computer configuration and 500 Incidents and 125 Change Requests for the 50,000-computer configuration were generated each hour, with three to four notification subscriptions and templates being processed for each incident and change request.
  • 一般來說,對於基準測試,通知訂閱處理和範本套用等工作流程會在每個工作項目產生後 1 分鐘內執行。Typically, in the baseline testing, workflows, such as notification subscription processing and template application, ran within one minute of each work item being generated.

如果您的組織計畫支援少於20000的電腦和主控台,以及較少的工作流程,即使某些 Service Manager 角色是裝載在虛擬機器上,您的 Service Manager 效能也是可以接受的。If your organization plans to have fewer than 20,000 supported computers and consoles and fewer workflows, your Service Manager performance should be acceptable, even if some of the Service Manager roles are hosted on virtual computers.

但是,如果您打算在 Service Manager 資料庫中新增其他支援的電腦,您應該規劃將 Service Manager 資料庫伺服器的 RAM 數量增加到本檔中所列的最低需求。However, if you plan to add additional supported computers in the Service Manager database, you should plan to increase the amount of RAM for the Service Manager database server beyond the minimum requirements listed in this document. 例如,在基準測試中,有 8 GB 的 RAM 安裝在包含20000電腦記錄的 Service Manager 資料庫伺服器中。For example, in the baseline test 8 GB of RAM was installed in the Service Manager database server that contained records for 20,000 computers. 然後,您應為計畫額外支援的 10,000 部電腦新增 8 GB 的 RAM。Afterward, you should add 8 GB of RAM for each increment of 10,000 of computers that you plan to support. 例如,您已針對 50,000 部電腦規劃 32 GB 的 RAM。For example, for 50,000 computers plan for 32 GB of RAM. 在執行 - SQL Server 的電腦上安裝 32 GB RAM 的50000電腦設定期間,相較于設定額外電腦之前的設定測試,效能已改善為不會再產生任何下降效果的狀態。During testing of the 50,000-computer configuration with 32 GB of RAM installed on the computer running SQL Server, performance was improved to a state where there was no longer any decreased effect compared to testing of the configuration before additional computers were added.

基準測試中也包含網路延遲的測試。Network latency was also tested in the baseline. Service Manager 主控台和 Service Manager 管理伺服器之間引進網路延遲。Network latency was introduced between the Service Manager console and the Service Manager management server.

注意

Service Manager 資料庫伺服器和 Service Manager 管理伺服器應位於低 - 延遲的 LAN 上; Service Manager 資料庫伺服器與 Service Manager 管理伺服器之間的網路延遲可能會大幅降低 Service Manager 效能。The Service Manager database server and Service Manager management servers should be on a low-latency LAN; network latency between the Service Manager database server and the Service Manager management server may lead to significant degradation of Service Manager performance.

測試另產生下列結果:The tests also delivered the following results:

  • 其中的網路延遲低於100毫秒 ( 毫秒 ) ,整體 Service Manager 的主控台回應時間就會很好。Where network latency was less than 100 milliseconds (msec), overall Service Manager console response times were found good.

  • 如果網路延遲是150到200毫秒,則會將效能標示為可用,而且 - 在某些情況下,回應時間最多可有40% 的效能降低。Where network latency was 150 to 200 msec, performance was noted as usable, with up to a 40-percent degradation in response time in some scenarios. 延遲150到200毫秒之間的延遲,您應該規劃評估組織的主要案例,並判斷遠端桌面連線 ( RDC 是否為較 ) 佳的選項。With latency between 150 to 200 msec, you should plan to evaluate the key scenarios for your organization and determine if Remote Desktop Connection (RDC) is a better option.

    注意

    在 Service Manager 主控台中擴充服務對應的延遲時間很慢。Expanding service maps in the Service Manager console was slow with any amount of latency.

  • 當網路延遲超過200毫秒時,整體 Service Manager 的主控台回應時間會被視為不良。When network latency exceeded 200 msec, overall Service Manager console response times were observed as poor. 如果延遲超過 200 毫秒,您應計劃使用 RDC 或其他類似的遠端存取解決方案進行操作工作。If your latency exceeds 200 msec, you should plan to use RDC or another similar remote access solution for operational tasks. 由於偶而執行的管理工作並不常見,因此您可能不需要遠端存取這些工作。However, because occasional administrative tasks are less common you might not need remote access for them.

後續步驟Next steps

  • 請參閱 Service Manager 的效能 ,以閱讀在規劃 Service Manager 軟體效能時應考慮的一般指導方針。Review Service Manager performance to read general guidelines to consider when you are planning for Service Manager software performance.