SharePoint Server 2013 的容量規劃Capacity planning for SharePoint Server 2013

摘要:了解如何規劃及管理容量與 SharePoint Server 2013 的效能。Summary: Learn how to plan and manage capacity and performance for SharePoint Server 2013.

本文說明如何規劃 SharePoint Server 2013 伺服器陣列的容量。當您有很好的感謝和容量規劃及管理的知識時,您可以套用您知識至系統大小調整。調整大小是用來描述選取項目及設定適當的資料架構、 邏輯及實體拓撲及硬體的解決方案平台的字詞。有一個範圍的容量管理和使用方式會影響您應該要如何判斷最適當的硬體和設定選項的考量。This article describes how to plan the capacity of a SharePoint Server 2013 farm. When you have a good appreciation and understanding of capacity planning and management, you can apply your knowledge to system sizing. Sizing is the term used to describe the selection and configuration of appropriate data architecture, logical and physical topology, and hardware for a solution platform. There is a range of capacity management and usage considerations that affect how you should determine the most appropriate hardware and configuration options.

閱讀本文之前,您應閱讀容量管理與調整大小概觀 (英文) SharePoint Server 2013Before you read this article, you should read Capacity management and sizing overview for SharePoint Server 2013.

重要

某些資訊及本文中的值為基礎的測試結果和 SharePoint 2010 產品與相關的其他資訊並不一定代表 SharePoint Server 2013 的最後一個值。Some information and values in this article are based on test results and other information related to SharePoint 2010 Products and may not represent the final values for SharePoint Server 2013.

在本文中,我們將說明您應針對自身的環境採取什麼步驟,以開始進行有效的容量管理。每個步驟都需要有某些必要資訊才能成功執行,且都會產生一組交付項目以供用於下個步驟。這些需求與交付項目將在下文針對每個步驟的介紹中以表格列出。In this article, we describe the steps you should take to undertake effective capacity management for your environment. Each step requires certain information for successful execution, and has a set of deliverables that you will use in the subsequent step. For each step, these requirements and deliverables are outlined in tables.

步驟 1:模型Step 1: Model

建立模型 SharePoint Server 2013 為基礎的環境開頭為分析您現有的方案和評估預期的需求和部署您的計劃要設定的對象。您啟動收集資訊使用者群、 資料需求、 延遲與輸送量目標並加以記載您想要部署的 SharePoint Server 2013 功能。使用此區段來了解您應收集哪些資料、 如何收集,及如何在後續步驟中使用。Modeling your SharePoint Server 2013-based environment begins with analyzing your existing solutions and estimating the expected demand and targets for the deployment you are planning to set up. You start by gathering information about your user base, data requirements, latency and throughput targets, and document the SharePoint Server 2013 features you want to deploy. Use this section to understand what data you should collect, how to collect it, and how it can be used in subsequent steps.

了解預期會有的工作負載與資料集Understand your expected workload and dataset

SharePoint Server 2013 實作的適當大小調整需要您研究並瞭解您解決方案的特性來處理預期的需求。了解需求需要您就可以同時說明工作負載特性等的使用者數目及最常用作業及內容的大小和內容分布等的資料集特性。Proper sizing of a SharePoint Server 2013 implementation requires that you study and understand the demand characteristics that your solution is expected to handle. Understanding the demand requires that you be able to describe both the workload characteristics such as number of users and the most frequently used operations, and dataset characteristics such as content size and content distribution.

本節將協助您了解所應收集的一些特定量值與參數,以及可用的收集機制。This section can help you understand some specific metrics and parameters you should collect and mechanisms by which they can be collected.

工作負載Workload

工作負載描述系統將必須承擔的需求、使用者群以及使用特性。下表提供一些有助於判斷工作負載的重要量值。您可以使用這張表格來記錄所收集到的這些量值。Workload describes the demand that the system will need to sustain, the user base and usage characteristics. The following table provides some key metrics that are helpful in determining your workload. You can use this table to record these metrics as you collect them.

工作量特性Workload Characteristics Value
平均每日 RPSAverage daily RPS
尖峰時間平均 RPSAverage RPS at peak time
每日單獨使用者總數Total number of unique users per day
每日平均並行使用者Average daily concurrent users
尖峰時間的尖峰並行使用者Peak concurrent users at peak time
每日要求總數Total number of requests per day
預期工作負載分布Expected workload distribution
每日要求數No. of Requests per day
網頁瀏覽器 - 搜尋編目Web Browser - Search Crawl
網頁瀏覽器 - 一般共同作業互動Web Browser - General Collaboration Interaction
網頁瀏覽器 - 社交互動Web Browser - Social Interaction
網頁瀏覽器 - 一般互動Web Browser - General Interaction
網頁瀏覽器 - Office Web 應用程式Web Browser - Office Web Apps
Office 用戶端Office Clients
OneNote 用戶端OneNote Client
SharePoint WorkspaceSharePoint Workspace
Outlook RSS 同步Outlook RSS Sync
Outlook Social ConnectorOutlook Social Connector
其他互動 (自訂應用程式/Web 服務)Other interactions(Custom Applications/Web services)
  • 並行使用者-是最常用來測量作業中為特定時段內產生要求的不同使用者人數在伺服器陣列上執行的並行。關鍵評量值是每日平均和尖峰負載並行使用者。Concurrent users - It is most common to measure the concurrency of operations executed on the server farm as the number of distinct users generating requests in a given time frame. The key metrics are the daily average and the concurrent users at peak load.

  • 每秒要求 (RPS) RPS 是用來描述伺服器陣列中的每秒,但沒有區別類型或大小的要求與伺服器陣列所處理的要求數表示上需求最常使用的標記。每個組織的使用者群會產生率取決於組織的唯一的使用狀況特性的系統負載。參閱這個詞字彙 (英文)一節中的容量管理與調整大小概觀 (英文) SharePoint Server 2013 的如需詳細資訊。Requests per second (RPS) - RPS is a commonly used indicator used to describe the demand on the server farm expressed in the number of requests processed by the farm per second, but with no differentiation between the type or size of requests. Every organization's user base generates system load at a rate that is dependent on the organization's unique usage characteristics. See the Glossary section in Capacity management and sizing overview for SharePoint Server 2013 for more information on this term.

  • 每日要求總數每日要求總數為系統將需要處理的整體負載的良好指標。它是最常用來測量驗證信號交換要求 (HTTP 狀態 401) 以外的所有要求透過在 24 小時期間內。Total daily requests - Total daily requests is a good indicator of the overall load the system will need to handle. It is most common to measure all requests except authentication handshake requests (HTTP status 401) over a 24 hour period.

  • 每日的使用者總數的使用者總數為系統將需要處理的整體負載的另一個索引鍵指示器。此度量單位設為實際的單獨使用者數在 24 小時期間內,不在組織中的員工的總數。Total daily users - Total users is another key indicator of the overall load the system will need to handle. This measurement is the actual number of unique users in a 24 hour period, not the total number of employees in the organization.

    注意

    每日使用者總計數目可以指出伺服器陣列上的負載增長潛力。例如,如果可能的使用者是 10 萬名員工,則每日 1 萬 5 千名使用者表示隨著使用者的採用情形增加,負載可能日益大幅增長。The number of total daily users can indicate the growth potential of the load on the farm. For example, if the number of potential users is 100k employees, 15k daily users indicates that the load may significantly grow over time as user adoption increases.

  • 工作負載分布-了解根據互動與伺服器陣列的用戶端應用程式要求的通訊群組可協助預測預期的趨勢和載入移轉至 SharePoint Server 2013 之後的變更。為使用者轉換到 Office 2013 及開始使用新的功能新負載等較新版的用戶端版本模式、 RPS 與總要求數被預期成長。我們可以針對每個用戶端會說明使用一天和伺服器上的用戶端或功能將會產生的總要求量的時段內的不同使用者人數。Workload Distribution - Understanding the distribution of the requests based on the clients applications that are interacting with the farm can help predict the expected trend and load changes after migrating to SharePoint Server 2013. As users transition to more recent client versions such as Office 2013, and start using the new capabilities new load patterns, RPS and total requests are expected to grow. For each client we can describe the number of distinct users using it in a time frame of a day, and the amount of total requests that the client or feature generates on the server.

    例如,下圖顯示提供一般社交解決方案的即時內部 Microsoft 環境在某一時刻的數據。在此例中,您可以看到大部份的負載都是因搜尋編目程式和一般的使用者網頁瀏覽行為而來。您也可以看到,Outlook Social Connector 功能 (佔 6.2% 的要求) 造成了顯著的負載。For example, the chart below shows a snapshot of a live internal Microsoft environment serving a typical social solution. In this example, you can see that the majority of the load is generated by the search crawler and typical end user web browsing. You can also observe that there is significant load introduced by the Outlook Social Connector feature (6.2 percent of the requests).

    一般每日負載分散要求數目

估計實際執行時的工作負載Estimating your production workload

在估計伺服器陣列必須能夠承擔的必要輸送量時,請先估計伺服器陣列中將使用哪些各種不同交易。請將重點放在分析系統將需要服務的最常用交易,了解其使用頻率,以及使用者人數。這些資料將有助您在稍後進行實際執行前測試時,驗證伺服器陣列是否能承受這類負載。In estimating the required throughput your farm needs to be able to sustain, begin with estimating the mix of transactions that will be used in your farm. Focus on analyzing the most frequently used transactions the system will serve, understanding how frequently they will be used and by how many users. That will help you validate later whether the farm can sustain such load in pre-production testing.

下圖說明工作負載與系統負載之間的關係:The following diagram describes the relationship of the workload and load on the system:

容量 - 工作負載圖表

若要估計預期的工作負載,請收集下列資訊:To estimate your expected workload, collect the following information:

  • 識別如典型的網頁瀏覽、 檔案下載及上傳、 Office Web 應用程式檢視及編輯瀏覽器中的使用者互動、 互動的共同撰寫、 SharePoint 工作區網站同步,Outlook 社交連線、 (在 Outlook 或其他 RSS 同步處理檢視者 」),PowerPoint 廣播、 OneNote 共用筆記本、 Excel Service 共用活頁簿,存取服務共用應用程式及其他人。請參閱如需詳細資訊的文章容量管理與調整大小概觀 (英文) SharePoint Server 2013 的服務和功能一節。整個計畫重心在識別可能會對您的部署唯一互動與辨識預期這類負載的影響、 範例可大幅使用 InfoPath 表單、 Excel Service 計算和類似的專用的解決方案。Identify user interactions such as typical web page browses, file downloads and uploads, Office Web Application views and edits in the browser, co-authoring interactions, SharePoint Workspace site syncs, Outlook Social Connections, RSS sync (in Outlook or other viewers), PowerPoint Broadcasts, OneNote shared notebooks, Excel Service shared workbooks, Access Service shared applications and others. See the Services and Features section of the article Capacity management and sizing overview for SharePoint Server 2013 for more information. Focus on the identifying the interactions that may be unique to your deployment, and recognize the expected impact of such load, examples can be significant use of InfoPath Forms, Excel Service Calculations and similar dedicated solutions.

  • 找出系統作業,例如搜尋累加編目、每日備份、設定檔同步計時器工作、Web 分析處理、記錄計時器工作等。Identify system operations such as Search incremental crawls, daily backups, profile sync timer jobs, web analytics processing, logging timer jobs and others.

  • 評估每日預計會使用每個功能的使用者總數、 衍生估計同時連線的使用者及高層級每第二該處要求已存在的並行等的 RPS 每個因素會讓您一些假設並行使用者的不同功能,您應該使用工作量表格稍早在本節中的估計。務必焦點在尖峰,而不是平均輸送量。規劃尖峰活動,就能夠 proper 大小為在 SharePoint Server 2013 為基礎的解決方案。Estimate the total number of users per day that are expected to utilize each capability, derive the estimated concurrent users and high level Requests per second, there are some assumptions you will be making such as present concurrency and the factor of RPS per concurrent users that is different across capabilities, you should use the workload table earlier in this section for your estimates. It is important to focus on peak hours, rather than average throughput. Planning for peak activity, you are able to proper size your SharePoint Server 2013-based solution.

如果您有現有的 Office SharePoint Server 2007 解決方案,您可以採擷 IIS 記錄檔或其他 Web 監視的工具必須以更了解從現有的方案的預期行為的部分或查看在下方] 區段中的指示來尋找更多詳細資料。如果您不從現有的解決方案移轉,您應該填寫使用粗略預估的資料表。在稍後步驟必須驗證假設並調整系統。If you have an existing Office SharePoint Server 2007 solution, you can mine the IIS log files or look to other Web monitoring tools you have to better understand some of the expected behaviors from the existing solution or see the instructions in the section below for more details. If you are not migrating from an existing solution, you should fill out the table using rough estimates. In later steps you will need to validate your assumptions and tune the system.

分析 SharePoint Server 2013 IIS 記錄檔Analyzing your SharePoint Server 2013 IIS Logs

若要探索現有的 SharePoint Server 2013 部署,例如多少使用者已啟用,如何嚴重相關的關鍵評量值使用系統種類的要求] 中的傳入以及從其來自用戶端類型,會需要將擷取的資料ULS 及 IIS 記錄檔]。其中一種簡單取得此資料是從 Microsoft 下載免費使用Log Parser、 功能強大的工具。Log Parser 可以讀取及寫入數字的文字及二進位格式,包括所有 IIS 格式。To discover key metrics about an existing SharePoint Server 2013 deployment, such as how many users are active, how heavily they are using the system, what kind of requests are coming in, and from what kind of clients they originate, it is necessary to extract data from ULS and IIS logs. One of the easiest ways to acquire this data is to use Log Parser, a powerful tool available free for download from Microsoft. Log Parser can read and write to a number of textual and binary formats, including all the IIS formats.

如需如何將 SharePoint Server 2013 使用記錄剖析器分析的詳細資訊,請閱讀分析 Microsoft SharePoint 產品和技術使用量(http://www.microsoft.com/downloads/details.aspx?familyid=f159af68-c3a3-413c-a3f7-2e0be6d5532e&英文 http://www.microsoft.com/downloads/details.aspx?familyid=718447d8-0814-427a-81c3-c9c3d84c456e&displaylang=en&tm)。For detailed information about how to analyze SharePoint Server 2013 usage using Log Parser, read Analyzing Microsoft SharePoint Products and Technologies Usage (http://www.microsoft.com/downloads/details.aspx?familyid=f159af68-c3a3-413c-a3f7-2e0be6d5532e&displaylang=en&tm).

您可以下載記錄剖析器 2.2 在http://www.microsoft.com/downloads/details.aspx?FamilyID=890CD06B-ABF8-4C25-91B2-F8D975CF8C07&英文 http://www.microsoft.com/downloads/details.aspx?familyid=718447d8-0814-427a-81c3-c9c3d84c456e&displaylang=enYou can download Log Parser 2.2 at http://www.microsoft.com/downloads/details.aspx?FamilyID=890CD06B-ABF8-4C25-91B2-F8D975CF8C07&displaylang=en.

資料集Dataset

資料集描述系統中儲存的內容量,以及這些內容在資料存放區中的散佈方式。下表提供一些有助判斷資料集的重要量值。您可以使用這張表格來記錄所收集到的這些量值。Dataset describes the volume of content stored in the system and how it can be distributed in the data store. The following table provides some key metrics that are helpful in determining your dataset. You can use this table to record these metrics as you collect them.

物件Object Value
資料庫大小 (GB)DB size (in GB)
內容資料庫數Number of Content DBs
網站集合數Number of site collections
Web 應用程式數Number of web apps
網站數Number of sites
搜尋索引大小 (項目數)Search index size (# of items)
文件數Number of docs
清單數Number of lists
網站平均大小Average size of sites
網站最大大小Largest site size
使用者設定檔數Number of user profiles
  • 內容大小-這瞭解您預期儲存在 SharePoint Server 2013 系統很重要的規劃和架構系統儲存空間及正確調整大小的搜尋解決方案所要編目和索引中的內容大小內容。磁碟空間總量說明內容的大小。如果您是從現有部署的移轉內容您可能會發現容易識別您要移動 ; 的總大小規劃時應該維持一段時間根據預測趨勢成長空間。Content size - Understanding the size of the content that you expect to store in the SharePoint Server 2013 system is important for planning and architecting the system storage, and also for properly sizing the Search solution that will crawl and index this content. The content size is described in total disk space. If you are migrating content from an existing deployment you might find it simple to identify the total size that you will move; while planning you should leave room for growth over time based on the predicted trend.

  • 總數的文件-資料主體大小以外,務必要追蹤整體的項目數。如果 100 GB 的資料組成與 100000 筆可為 1 kb 每個檔案 50 檔 2 GB 的系統反應以不同方式。中大型部署,單一項目、 文件或區域中的文件有較少壓力會是較佳的效能。廣泛分散式 like 許多網站和網站集合跨多個較小的檔案內容會比較容易做然後單一大型文件庫具有極大的檔案。Total number of documents - Other than the data corpus size, it is important to track the overall number of items. The system reacts differently if 100 GB of data is composed of 50 files of 2 GB each versus 100,000 files of 1 KB each. In large deployments, the less stress there is on a single item, document or area of documents, the better performance will be. Widely distributed content like multiple smaller files across many sites and site collection is easier to serve then a single large document library with very large files.

  • 網站集合大小上限-請務必識別功能將會儲存在 SharePoint Server 2013; 內容的最大單位通常是組織需要在禁止分割該內容的單位。所有網站集合和網站集合的估計的總數的平均大小是可協助您識別您偏好的資料架構的其他指標。Maximum site collection size - It is important to identify what is the biggest unit of content that you will store in SharePoint Server 2013; usually it is an organizational need that prevents you from splitting that unit of content. Average size of all site collections and the estimated total number of site collections are additional indicators that will help you identify your preferred data architecture.

  • 服務應用程式資料特性-除了分析對內容存放區、 儲存需求您應該分析並估計包括其他 SharePoint Server 2013 存放區的大小:Service applications data characteristics - In addition to analysing the storage needs for the content store, you should analyse and estimate the sizes of other SharePoint Server 2013 stores, including:

  • 搜尋索引總大小Total size of the Search index

  • 以設定檔儲存中的使用者數為基礎的設定檔資料庫總大小The profile database total size based on the number of user in the profile store

  • 以預期會有之標記、同事與活動數為基礎的社交資料庫總大小The social database total size based on the expected number of tags, colleagues and activities

  • 中繼資料存放區大小The metadata store size

  • 使用量資料庫大小The size of the usage database

  • Web Analytics 資料庫大小The size of the Web Analytics data base

設定伺服器陣列效能與可靠性目標Setting Farm Performance and Reliability Targets

其中一個的可傳送作業步驟 1: 模型是確實了解的效能與可靠性目標的配合組織的需求。適當地設計的 SharePoint Server 2013 解決方案應該能夠達成"四個 9"(99.99%) 的上線時間百分比小於一秒伺服器回應速度。One of the deliverables of Step 1: Model is a good understanding of the performance and reliability targets that best fit the needs of your organization. A properly designed SharePoint Server 2013 solution should be able to achieve "four nines" (99.99%) of uptime with sub-second server responsiveness.

用來描述伺服器陣列之效能與可靠性的指標可包括:The indicators used to describe the performance and reliability of the farm can include:

  • 伺服器可用性-通常所述的系統的整體上線時間百分比。您應該追蹤任何未預期的停機時間和比較整體可用性要設為您設定組織目標。(亦即為 99%、 達 99.9%、 99.99%) 常目標說明依照 9 的數目Server availability - Usually described by the percent of overall uptime of the system. You should track any unexpected downtime and compare the overall availability to the organizational target you set. The targets are commonly described by a number of nines (i.e. 99%, 99.9%, 99.99%)

  • 伺服器回應速度-在伺服器陣列以服務要求所花費的時間會追蹤伺服器陣列的狀況良好的指標。這個指示器命名伺服器端延遲,通常為很常使用的平均或正在所服務的每日要求的中間 (第 50 個百分位數) 延遲。目標常所述子秒數。請注意,如果您的組織有以從 SharePoint Server 2013 服務頁面中低於兩秒的目標伺服器端目標必須是子離開連絡用戶端透過網路] 頁面上的時間和瀏覽器中呈現的秒數。也通常較長的伺服器回應時間會指示不健康的伺服器陣列,這通常是對輸送量的影響為並少可以 RPS 跟如果您在大部分的要求在伺服器上花多個秒Server responsiveness - The time it takes the farm to serve requests is a good indicator to track the health of the farm. This indicator is usually named server side latency, and it is common to use the average or median (the 50th percentile) latency of the daily requests being served. The targets are commonly described in sub seconds or seconds. Note that if your organization has a target to serve pages from SharePoint Server 2013 in less than two seconds, then the server side goal needs to be sub seconds to leave time for the page to reach the client over the network and time to render in the browser. Also in general longer server response times are an indication of an unhealthy farm, as this usually as an impact on throughput and rarely can RPS keep up if you spend more than a second on the server on most requests

  • 伺服器 spikiness另一種很好的伺服器端延遲指示器值得追蹤是所有要求的速度最慢的 5%的行為。較慢的要求通常是較高的負載下時瀏覽系統要求或甚至更常受到較不需要經常活動發生時使用者互動與系統; 的要求狀況良好的系統是一個具有最慢的要求,以及加以控制。的目標類似伺服器回應速度,但是若要達到伺服器 spikiness 上的小於一秒回應,您必須建立具有許多備用資源來處理的負載暴增的系統。Server spikiness - Another good server side latency indicator worth tracking is the behaviour of the slowest 5% of all requests. Slower requests are usually the requests that hit the system when it is under higher load or even more commonly, requests that are impacted by less frequent activity that occur while users interact with the system; a healthy system is one that has the slowest requests under control as well. The target here is similar to Server Responsiveness, but to achieve sub-second response on server spikiness, you will need to build the system with a lot of spare resources to handle the spikes in load.

  • 系統資源使用率-用來追蹤系統的狀況其他一般指標會指出在伺服器陣列拓撲的每個伺服器的健全狀況的系統計數器的集合。追蹤最常使用的指標是 %cpu 使用量及可用記憶體;不過,有數個其他計數器可以協助識別非狀況良好的系統;在可以找到更多詳細資料步驟 5: 監視與維護System resource utilization - Other common indicators used to track the health of the system are a collection of system counters that indicate the health of each server in the farm topology. The most frequently used indicators to track are % CPU utilization and Available Memory; however, there are several additional counters that can help identify a non-healthy system; more details can be found in Step 5: Monitor and Maintain.

步驟 2:設計Step 2: Design

您已針對需要提供的解決方案收集好現況資料或估計值,現在可以進入下個步驟,開始設計預料能夠承擔所預期需求的架構。Now that you have finished collecting some facts or estimates on the solution you need to deliver, you are ready to start the next step of designing a proposed architecture that you predict will be able to sustain the expected demand.

此步驟結束時,您應該會得出一份實體拓撲設計和邏輯拓撲配置,供您進一步進行必要的採購。By the end of this step you should have a design for your physical topology and a layout for your logical topology, so you should be able to go ahead with any necessary purchase orders.

硬體規格和您配置的電腦數緊密相關,為了處理特定負載,您可以選擇部署的解決方案有數種。常見的用法是使用少數幾部強大電腦 (垂直擴充) 或多部小型電腦 (向外擴充);每種解決方案在容量、備援、電力、成本、空間和其他考量方面各有其優缺點。The hardware specifications and the number of machines you layout are tightly related, to handle a specific load there are several solutions you can choose to deploy. It is common to either use a small set of strong machines (scale up) or a larger set of smaller machines (scale out); each solution has its advantages and disadvantages when it comes to capacity, redundancy, power, cost, space, and other considerations.

在此步驟,建議您先從決定架構和拓撲開始。先定義您要如何配置不同的伺服器陣列以及各伺服器陣列中的不同服務,然後為設計中的每部伺服器選擇適當的硬體規格。您也可以先找出您要部署的硬體規格 (許多組織受限於特定的公司標準),然後再定義架構和拓撲。We recommend that you begin this step by determining your architecture and topology. Define how you plan to layout the different farms and the different services in each farm, and then pick the hardware specifications for each of the individual servers in your design. You can also execute this process by identifying the hardware specifications you are expected to deploy (many organizations are constrained to a certain company standard) and then define your architecture and topology.

請使用下表記錄您的設計參數。表中資料為範例資料,只用來示範如何用此表記錄資料,不應用來決定您的伺服器陣列大小。Use the following table to record your design parameters. The data included is sample data, and should not be used to size your farm. It is intended to demonstrate how to use this table for your own data.

角色Role 類型 (標準或虛擬)Type (Standard or virtual) 機器數目# of machines 程序Procs RAMRAM IOPS 需求IOPS need 磁碟大小 OS + LogDisk size OS+Log 資料磁碟Data drive
網頁伺服器Web servers
虛擬Virtual
44
4 個核心4 cores
88
N/A
400 GB400 GB
N/A
內容資料庫伺服器Content database server
標準Standard
1 個叢集1 cluster
4 個四核心 2.33 (GHz)4 quad-core 2.33 (GHz)
4848
2 k2k
400 GB400 GB
20 個 300 GB 磁碟20 disks of 300GB
@ 15K RPM@ 15K RPM
應用程式伺服器Application servers
虛擬Virtual
44
4 個核心4 cores
1616
N/A
400 GB400 GB
N/A
搜尋編目目標網頁伺服器Search Crawl Target Web server
虛擬Virtual
11
4 個核心4 cores
88
N/A
400 GB400 GB
N/A
搜尋查詢伺服器Search Query server
標準Standard
22
2 個四核心 2.33 (GHz)2 quad-core 2.33 (GHz)
3232
N/A
400 GB400 GB
500 GB500 GB
搜尋編目程式伺服器Search Crawler server
標準Standard
22
2 個四核心 2.33 (GHz)2 quad-core 2.33 (GHz)
1616
400400
400 GB400 GB
N/A
搜尋編目資料庫伺服器Search Crawl database server
標準Standard
1 個叢集1 cluster
4 個四核心 2.33 (GHz)4 quad-core 2.33 (GHz)
4848
4k (針對讀取調整)4k (tuned for read)
100 GB100 GB
16 個 150 GB 磁碟 @ 15K RPM16 disks of 150GB @ 15K RPM
搜尋屬性儲存區資料庫 + 管理資料庫伺服器Search Property Store database + Administration database server
標準Standard
1 個叢集1 cluster
4 個四核心 2.33 (GHz)4 quad-core 2.33 (GHz)
4848
2 k (針對寫入調整)2k (tuned for write)
100 GB100 GB
16 個 150 GB 磁碟 @ 15K RPM16 disks of 150GB @ 15K RPM

決定起始架構Determine your starting point architecture

本節說明如何選擇起始架構。This section describes how to select a starting point architecture.

當您部署 SharePoint Server 2013 時,您可以實作解決方案; 選擇從某個範圍的拓撲您可能會對叢集或鏡像資料庫伺服器和小心謹慎應用程式的各種服務 SharePoint Server 2013 伺服器陣列部署單一伺服器或向外延展多部伺服器。稍後即會選取根據每個角色,根據您的容量、 可用性及備援需求需求的硬體設定。When you deploy SharePoint Server 2013, you can choose from a range of topologies to implement your solution; you may deploy a single server or scale out many servers to a SharePoint Server 2013 farm with clustered or mirrored database servers and discreet application servers for various services. Later you will select the hardware configurations based on the requirements of each of the roles, based on your capacity, availability, and redundancy needs.

啟動檢閱不同參考架構和了解您的伺服器陣列結構、 決定是否應該分割跨多個伺服器陣列,您的解決方案或同盟某些服務,例如 search、 專用伺服器陣列上。請參閱 <參考架構一節中的容量管理與調整大小概觀 (英文) SharePoint Server 2013 的如需詳細資訊。Start by reviewing the different reference architectures and figure out your farm structure, decide if you should split your solution across multiple farms, or federate some services, such as search, on a dedicated farm. See the Reference Architectures section in Capacity management and sizing overview for SharePoint Server 2013 for more information.

SharePoint Server 2010 技術案例研究SharePoint Server 2010 Technical Case Studies

SharePoint Server 2013 的容量管理指導包括數量的現有呈現現有的 SharePoint Server 2013 為基礎的實際執行環境的詳細的描述的實際執行環境技術案例研究。只要有; 發佈至 SharePoint Server 2013 的技術案例研究特定現有的 SharePoint Server 2010 案例研究可做為如何設計 SharePoint Server 2013 為基礎的環境的特定用途的參照。Capacity management guidance for SharePoint Server 2013 includes a number of technical case studies of existing production environments that present a detailed description of existing SharePoint Server 2013-based production environments. Technical case studies specific to SharePoint Server 2013 will be published as they become available; the existing SharePoint Server 2010 case studies can serve as a reference on how to design a SharePoint Server 2013-based environment for specific purposes.

您可以使用這些案例研究為參照時特別是如果您會找到這些部署特定的重要差異描述類似的需求與您的解決方案的目標設計您的 SharePoint Server 2013 解決方案的架構架構。You can use these case studies as a reference while designing the architecture of your SharePoint Server 2013 solutions especially if you find the description of these deployment specific key differentiators similar to the demands and targets of the solution you are architecting.

這些文件會針對每個所記載的案例研究,說明下列資訊:These documents describe the following information for each documented case study:

  • 規格,如硬體、 伺服器陣列拓撲及設定 ;Specifications, such as hardware, farm topology and configuration;

  • 工作量: 包括使用者群與使用特性 ;Workload including the user base, and the usage characteristics;

  • 資料集,包括內容大小、 內容特性和內容分布Dataset, including contents sizes, content characteristics and content distribution

  • 狀況與效能包含一組說明伺服器陣列的可靠性及效能特性記錄的指標Health and performance including a set of recorded indicators describing the farm's reliability and performance characteristics

如需詳細資訊,請從效能與容量技術案例研究 (SharePoint Server 2010)頁面下載相關文件。For more information, download relevant documents from the Performance and capacity technical case studies (SharePoint Server 2010) page.

選擇硬體Select your hardware

為伺服器陣列中的電腦選擇適當規格十分重要,這可確保您的部署展現適當的可靠性與效能,請務必謹記您應針對尖峰負載和尖峰時間進行規劃,換句話說,當您的伺服器陣列在平均負載情形下執行時,仍應有足夠的資源可用來處理最大預期需求,同時仍符合延遲和輸送量目標。Selecting the right specifications for the machines in your farm is a crucial step to ensure proper reliability and performance of your deployment, one key concept to keep in mind is that you should plan for peak load and peak hours; in other words, when your farm is operating under average load conditions, there should be enough resources available to handle the greatest expected demand while still hitting latency and throughput targets.

伺服器的核心容量和效能硬體功能反映四個主要類別:系統的處理能力、磁碟效能、網路容量和記憶體功能。The core capacity and performance hardware features of servers reflect four main categories: processing power, disk performance, network capacity, and memory capabilities of a system.

另外還需要考慮使用虛擬的機器。可以使用虛擬機器來部署 SharePoint Server 2013 伺服器陣列。雖然尚未新增任何效能好處找到虛擬化,它提供可管理性優點。虛擬化 SQL Server 型電腦通常不建議使用,但仍有某些優點,虛擬化的網頁伺服器與應用程式伺服器層。如需詳細資訊,請參閱虛擬化規劃(https://technet.microsoft.com/en-us/library/71c203cd-7534-47b0-9122-657d72ff0080(Office.14).aspx)。Another thing to consider is using virtualized machines. A SharePoint Server 2013 farm can be deployed using virtual machines. Although virtualization has not been found to add any performance benefits, it does provide manageability benefits. Virtualizing SQL Server-based computers is generally not recommended, but there may be certain benefits to virtualizing the Web server and application server tiers. For more information, see Virtualization planning (https://technet.microsoft.com/en-us/library/71c203cd-7534-47b0-9122-657d72ff0080(Office.14).aspx).

如需硬體需求的詳細資訊,請參閱 < SharePoint Server 2016 的硬體和軟體需求For more information about hardware requirements, see Hardware and software requirements for SharePoint Server 2016.

硬體選擇指導方針Hardware Selection Guidelines

選擇處理器Choosing Processors

SharePoint Server 2013 是僅適用於 64 位元處理器。一般而言,多個處理器可讓您提供更大的需求。SharePoint Server 2013 is available only for 64-bit processors. In general, more processors will enable you to serve greater demand.

當您將新增更多核心 SharePoint Server 2013,個別 web 伺服器會向上擴充。更多核心的伺服器有其可以維持,所有其他正在相等的更多負載。在大型的 SharePoint Server 2013 部署中,我們建議您配置多部 4 核心網頁伺服器 (這可以虛擬化),或更少更有力 (8-位 / 16 / 24 核心) 網頁伺服器。In SharePoint Server 2013, individual web servers will scale up as you add more cores. The more cores the server has the more load it can sustain, all else being equal. In large SharePoint Server 2013 deployments, we recommend that you allocate either multiple 4-core web servers (which can be virtualized), or fewer stronger (8-/16-/24-cores) web servers.

應用程式伺服器的處理器容量需求會根據伺服器與執行服務角色有所不同。SharePoint Server 2013 的一些功能的需求與其他更大的處理能力。例如,SharePoint Search Service 是高度取決於應用程式伺服器的處理能力。Application servers' processor capacity requirements differ depending on the role of the server and the services it is running. Some SharePoint Server 2013 features demand greater processing power than others. For example, the SharePoint Search Service is highly dependent on the processing power of the application server.

SQL Server 的處理器容量需求也取決於 SQL Server 電腦所裝載的服務資料庫。The processor capacity requirements for SQL Server also depend on the service databases that a SQL Server-based computer is hosting.

選擇記憶體Choosing Memory

您的伺服器需要不同的記憶體,根據伺服器的函數和角色金額。例如,執行搜尋編目元件的伺服器會處理資料更快速地如果因為文件讀入記憶體處理有大量的記憶體。運用 SharePoint Server 2013 的快取功能的許多的網頁伺服器可能需要更多的記憶體。Your servers will require varying amounts of memory, depending on server function and role. For example, servers that run Search crawl components will process data more quickly if they have a large amount of memory because documents are read into memory for processing. Web servers that take advantage of many of the caching features of SharePoint Server 2013 may require more memory as well.

一般而言,web 伺服器的記憶體需求所高度取決於伺服器陣列中啟用的應用程式集區的數目和正在所服務的並行要求數目。在大多數的實際執行 SharePoint Server 2013 部署中,我們建議您配置至少需要 8 GB RAM 每個網頁伺服器上,使用有更大的流量的伺服器的建議使用 16 GB 或使用多個應用程式集區部署設定的隔離。In general, web server memory requirements are highly dependent on the number of application pools enabled in the farm and the number of concurrent requests being served. In most production SharePoint Server 2013 deployments, we recommend that you allocate at least 8 GB RAM on each web server, with 16 GB recommended for servers that have greater traffic or deployments with multiple application pools set up for isolation.

應用程式伺服器的記憶體需求也; 不同SharePoint Server 2013 的一些功能比其他應用程式層上有更大的記憶體需求。在大部分的實際執行 SharePoint Server 2013 部署我們建議您配置至少需要 8 GB RAM 上每個應用程式伺服器16 GB、 32 GB 和 64 GB 應用程式伺服器是一般啟用許多應用程式服務之後的同一部伺服器,或啟用高度取決於記憶體,例如 Excel Calculation Service 和 SharePoint Server 2013 搜尋服務的服務。Application servers' memory requirements differ also; some SharePoint Server 2013 features have greater memory requirements on the application tier than others. In most production SharePoint Server 2013 deployments we recommend that you allocate at least 8 GB RAM on each application server; 16 GB, 32 GB and 64 GB application servers are common when many application services are enabled on the same server, or when services that are highly dependent on memory, such as the Excel Calculation Service and SharePoint Server 2013 Search Service, are enabled.

資料庫伺服器的記憶體需求會變得更密切仰賴資料庫大小。如需選擇 SQL Server 型電腦的記憶體的詳細資訊,請參閱Storage and SQL Server capacity planning and configuration (SharePoint Server)。The memory requirements of database servers are tightly dependent on the database sizes. For more information about choosing memory for your SQL Server-based computers, see Storage and SQL Server capacity planning and configuration (SharePoint Server).

選擇網路Choosing Networks

分散式伺服器陣列除了可讓網路上的用戶端快速存取到資料來節省使用者時間之外,也必須讓伺服器間的通訊享有快速存取速度。當您將服務分散到多部伺服器或是將某些服務與其他伺服器陣列結為同盟時,就更是需要如此。在伺服器陣列中,網頁伺服器層、應用程式伺服器層和資料庫伺服器層之間會有顯著流量,因此在處理極大型檔案或極高負載等情形下,網路很容易就會變成整個流程當中的瓶頸。In addition to the benefit offered to users if clients have fast data access through the network, a distributed farm must have fast access for inter-server communication. This is especially true when you distribute services across multiple servers or federate some services to other farms. There is significant traffic in a farm across the web server tier, the application server tier, and the database server tier, and network can easily become a bottleneck under certain conditions like dealing with very large files or very high loads.

Web 伺服器和應用程式應該設定為使用至少兩個網路介面卡 (Nic): 一個處理使用者流量,另處理伺服器間通訊的 NIC。伺服器之間的網路延遲有大幅影響效能。因此,務必維護的網頁伺服器及裝載內容資料庫的 SQL Server 型電腦之間的網路延遲小於 1 毫秒。主控每個服務應用程式資料庫的 SQL Server 型電腦應盡可能使用的應用程式伺服器也。伺服器陣列的伺服器之間的網路應該會有至少 1 Gbps 的頻寬。Web servers and application servers should be configured to use at least two network interface cards (NICs): one NIC to handle end-user traffic and the other to handle the inter-server communication. Network latency between servers can have a significant effect on performance. Therefore, it is important to maintain less than 1 millisecond of network latency between the web server and the SQL Server-based computers hosting the content databases. The SQL Server-based computers that host each service application database should be as close as possible to the consuming application server also. The network between farm servers should have at least 1 Gbps of bandwidth.

選擇磁碟及儲存設備Choosing Disks and Storage

所謂磁碟管理不只是在想辦法為資料提供足夠的空間。您必須考慮到後續的需求與成長,確定儲存區架構不會拖慢系統速度。請務必確保每個磁碟上至少具備 30% 的額外容量 (高於預估的最高資料需求),以預留空間來因應未來的成長。此外,在大部分實際執行環境中,磁碟速度 (IOps) 對於提供足夠輸送量來滿足伺服器儲存需求相當重要。您必須預估所部署的主要資料庫將需要的流量數量 (IOps),並配置足夠磁碟來滿足該流量。Disk management is not simply a function of providing sufficient space for your data. You must assess the on-going demand and growth, and make sure that that the storage architecture is not slowing the system down. You should always make sure that that you have at least 30 percent additional capacity on each disk, above your highest data requirement estimate, to leave room for future growth. Additionally, in most production environments, disk speed (IOps) is crucial to providing sufficient throughput to satisfy the servers' storage demands. You must estimate the amount of traffic (IOps) the major databases will require in your deployment and allocate enough disks to satisfy that traffic.

如需如何選擇資料庫伺服器磁碟的詳細資訊,請參閱Storage and SQL Server capacity planning and configuration (SharePoint Server)。For more information about how to choose disks for database servers, see Storage and SQL Server capacity planning and configuration (SharePoint Server).

網頁伺服器和應用程式伺服器也有儲存需求。在大部分實際執行環境中,建議您至少配置 200 GB 磁碟空間來容納作業系統,並配置 150 GB 磁碟空間來容納記錄檔。The web and application servers have storage requirements also. In most production environments, we recommend that you allocate at least 200 GB disk space for OS and temp and 150 GB of disk space for logs.

步驟 3:試驗、測試和最佳化Step 3: Pilot, Test and Optimize

測試和最佳化階段是有效的容量管理變得極為重要元件。您應測試新架構再將其部署至實際執行環境與您應該進行接受度測試與下列監控的最佳作法以確保您設計的架構達到效能與容量目標。這可讓您識別和最佳化的潛在瓶頸之前影響即時部署中的使用者。如果您要從 Office SharePoint Server 2007 環境及計劃進行結構變更升級或所評估的 SharePoint Server 2013 新功能的使用者負載,然後測試特別重要,確認新的 SharePoint Server2013 為基礎的環境會符合效能和容量目標。The testing and optimization stage is an extremely important component of effective capacity management. You should test new architectures before you deploy them to production and you should conduct acceptance testing together with following monitoring best practices in order to ensure the architectures you design achieve the performance and capacity targets. This allows you to identify and optimize potential bottlenecks before they affect users in a live deployment. If you are upgrading from an Office SharePoint Server 2007 environment and plan to make architectural changes, or are estimating user load of the new SharePoint Server 2013 features, then testing particularly important to make sure that your new SharePoint Server 2013-based environment will meet performance and capacity targets.

一旦您已測試您的環境,您可以分析測試結果,以決定會有什麼變更必須進行以達到效能與容量所談的是您在建立步驟 1: 模型Once you have tested your environment, you can analyze the test results to determine what changes must be made in order to achieve the performance and capacity targets you established in Step 1: Model.

以下是在實際執行前,應遵循操作的建議子步驟:These are the recommended sub steps that you should follow for pre-production:

  • 建立測試環境,模擬您在設計的初始架構步驟 2: 設計Create the test environment that mimics the initial architecture you designed in Step 2: Design.

  • 填入存放區的資料集或您已識別中的資料集的一部分步驟 1: 模型Populate the storage with the dataset or part of the dataset that you've identified in Step 1: Model.

  • 對系統施加代表已中所識別之工作量的綜合負載電腦步驟 1: 模型Stress the system with synthetic load that represents the workload you've identified in Step 1: Model.

  • 執行測試、分析、結果,並最佳化您的架構。Run tests, analyze results, and optimize your architecture.

  • 將最佳化後的架構部署至資料中心,並讓一小群使用者試驗。Deploy your optimized architecture in your data center, and roll out a pilot with a smaller set of users.

  • 分析試驗結果、找出潛在瓶頸,然後對架構進行最佳化。必要時再重新測試一遍。Analyze the pilot results, identify potential bottlenecks, and optimize the architecture. Retest if it is required.

  • 部署至實際執行環境。Deploy to the production environment.

測試Test

測試都是 critial 中建立您的系統設計以支援您的工作負載和使用狀況特性的能力。如需如何測試您的 SharePoint Server 2013 部署的詳細資訊,請參閱SharePoint Server 2013 效能測試Testing is a critial factor in establishing the ability of your system design to support your workload and usage characteristics. See Performance testing for SharePoint Server 2013 for detailed information about how to test your SharePoint Server 2013 deployment.

  • 建立測試計劃Create a test plan

  • 建立測試環境Create the test environment

  • 建立測試和工具Create Tests and Tools

部署試驗環境Deploy the pilot environment

SharePoint Server 2013 部署至實際執行環境之前,請務必您先部署試驗環境及徹底測試以確定它可符合容量和效能目標您預期尖峰負載伺服器陣列。建議的綜合負載特別適用於大型部署請先測試以及然後負荷的即時使用者和即時內容一小群試驗環境。使用一小群 live 使用者分析試驗環境的優點是驗證完全移入實際執行環境之前需使用狀況特性和內容的成長做一些假設有機會。Before you deploy SharePoint Server 2013 to a production environment, it is important that you first deploy a pilot environment and thoroughly test the farm to make sure that that it can meet capacity and performance targets for your expected peak load. We recommend that the pilot environment is first tested with synthetic load especially for large deployments, and then stressed by a small set of live users and live content. The benefit of analyzing a pilot environment by using a small set of live users is the opportunity to validate some assumptions you made about the usage characteristics and the content growth before you go fully into production.

最佳化Optimize

如果就算擴充伺服器陣列硬體或進行拓撲變更,都無助於達到您的效能與容量目標,您應考慮修改解決方案。例如,如果您最初的需求是以單一伺服器陣列提供共同作業、搜尋和社交功能,則您可能需將某些服務 (如搜尋) 與專門的服務伺服器陣列結成同盟,或是將工作負載分割給多個伺服器陣列。另一個替代方案是部署一個專門的伺服器陣列來提供社交功能,再部署另一個來提供小組共同作業功能。If you cannot meet your capacity and performance targets by scaling your farm hardware or making changes to the topology, you may have to consider revising your solution. For example, if your initial requirements were for a single farm for collaboration, Search and Social, you may have to federate some services such as search to a dedicated services farm, or split the workload across more farms. One alternative is to deploy a dedicated farm for social and another for team collaboration.

步驟 4:部署Step 4: Deploy

一旦您在執行測試您最終循並確認您所選取的架構可獲得效能和容量所談的是您在建立步驟 1: 模型,您可以部署至 SharePoint Server 2013 型環境實際執行。Once you have executed your final round of tests and confirmed that the architecture you have selected can achieve the performance and capacity targets you established in Step 1: Model, you can deploy your SharePoint Server 2013-based environment to production.

適當的導入策略目視環境和情況。雖然 SharePoint Server 2013 部署通常是此文件的範圍之外,有可能會超出容量計劃練習甚至某些建議的活動。以下是一些範例:The appropriate rollout strategy will vary depending on the environment and situation. While SharePoint Server 2013 deployment generally is outside the scope of this document, there are certain suggested activities that may come out of the capacity planning exercise. Here are some examples:

  • 部署新的 SharePoint Server 2013 伺服器陣列:容量計劃練習應該具有引導及確認設計及部署 SharePoint Server 2016 計劃。在此例中首度發行將第一個廣泛部署 SharePoint Server 2013。需要移動或重建伺服器和入實際執行環境的容量規劃練習期間所使用的服務。這會是最直覺案例是因為沒有任何升級或修改現有的伺服器陣列所需。Deploying a new SharePoint Server 2013 farm: The capacity planning exercise should have guided and confirmed plans for a design and deployment of SharePoint Server 2016. In this case, the rollout will be the first broad deployment of SharePoint Server 2013. It will require moving or rebuilding the servers and services that were used during the capacity planning exercises into production. This is the most straight-forward scenario because there are not any upgrades or modifications needed to an existing farm.

  • 將 Office SharePoint Server 2007 伺服器陣列升級至 SharePoint Server 2013:容量計劃練習應該具有驗證設計的伺服器陣列可以符合現有的要求和規模設定以滿足需求的增加與 SharePoint Server 2013 伺服器陣列的流量。一部分的容量規劃練習應該包含測試移轉來驗證升級程序將花費,任何自訂程式碼必須修改或取代,是否要更新等等的結論在有任何協力廠商工具容量規劃您應該有已驗證的設計和了解多少花費的時間它將會以升級及規劃如何以搭配使用透過升級程序-例如最佳就地升級,或是移轉內容資料庫至新的伺服器陣列。如果您正在進行期間容量規劃您可能會找到該會需要額外或已升級的硬體,然後在就地升級及的停機時間考量。規劃練習的輸出的一部分應為所需的硬體變更清單並部署之硬體的詳細計劃先變更伺服器陣列。已驗證期間容量規劃的硬體平台備妥後,您可以使用升級至 SharePoint Server 2013 的程序向前移動。Upgrading an Office SharePoint Server 2007 farm to SharePoint Server 2013: The capacity planning exercise should have validated the design for a farm that can meet existing demands and scale up to meet increased demand and usage of a SharePoint Server 2013 farm. Part of the capacity planning exercise should have included test migrations to validate how long the upgrade process will take, whether any custom code must be modified or replaced, whether any third-party tools have to be updated, and so on At the conclusion of capacity planning you should have a validated design, and understanding of how much time that it will take to upgrade, and a plan for how best to work through the upgrade process - for example, an in-place upgrade, or migrating content databases into a new farm. If you're doing an in-place upgrade then during capacity planning you may have found that additional or upgraded hardware will be needed, and considerations for downtime. Part of the output from the planning exercise should be a list of the hardware changes that are needed and a detailed plan to deploy the hardware changes to the farm first. Once the hardware platform that was validated during capacity planning is in place, you can move forward with the process of upgrading to SharePoint Server 2013.

  • 提升效能的現有的 SharePoint Server 2013 伺服器陣列:容量計劃練習應該有幫助您找出在您目前的實作瓶頸、 規劃減少或消除這些瓶頸、 方法及驗證符合您的業務需求 for SharePoint 的增強的實作Server 2013 服務。有不同的方式在其中的效能問題可能已解決,從一件容易重新配置跨現有硬體、 升級現有的硬體,或新增額外的硬體及新增其他服務的服務為某個項目。不同的方法應該測試及驗證期間的容量規劃練習,並視結果而定的部署計畫設計然後用此測試。Improving the performance of an existing SharePoint Server 2013 farm: The capacity planning exercise should have helped you to identify the bottlenecks in your current implementation, plan ways to reduce or eliminate those bottlenecks, and validate an improved implementation that meets your business requirements for SharePoint Server 2013 services. There are different ways in which performance issues could have been resolved, from something as easy as reallocating services across existing hardware, upgrading existing hardware, or adding additional hardware and adding additional services to it. The different approaches should be tested and validated during the capacity planning exercise, and then a deployment plan designed depending on the results of that testing.

步驟 5:監視和維護Step 5: Monitor and Maintain

為了維持系統效能,您必須監視伺服器以找出潛在的瓶頸。若要能夠有效進行監視,您必須先了解哪些重要指標可以指出伺服器陣列某個部份需要注意,並且知道如何解讀指標。如果您發現伺服器陣列的運作不符合自己所定義的目標,可以調整伺服器陣列,例如新增或移除硬體資源、變更拓撲,或是變更資料儲存方式。To maintain system performance, you must monitor your server to identify potential bottlenecks. Before you can monitor effectively, you must understand the key indicators that will tell you if a specific part of your farm requires attention, and know how to interpret these indicators. If you find that your farm is operating outside the targets you have defined, you can adjust your farm by adding or removing hardware resources, changing your topology, or changing how data is stored.

請參閱監視和維護 SharePoint Server 2013您可以變更可協助您決定是否需要的任何變更其早期分階段監視環境之設定的清單。請記住,增加您監視功能會影響您的使用狀況資料庫需要多少磁碟空間。一旦環境的穩定性及此詳細監控已不再需要,您可能會想要回復下方的設定為其預設設定。See Monitoring and maintaining SharePoint Server 2013 for a list of the settings that you can change to monitor your environment in its early stages, which will help you determine whether any changes are needed. Keep in mind that increasing your monitoring capabilities will affect how much disk space that your usage database will require. Once the environment is stable and this detailed monitoring is no longer required, you may want to reverse the settings below to their default settings.

如需有關狀況監視與疑難排解使用狀況監視工具進行介面內建 SharePoint Server 2013 管理中心,閱讀下列文章:For more information about health monitoring and troubleshooting using the health monitoring tools built into the SharePoint Server 2013 Central Admin interface, read the following:

SharePoint Server 2016 中的監視與報告Monitoring and Reporting in SharePoint Server

解決問題與疑難排解(https://technet.microsoft.com/en-us/library/ee748639(office.14).aspx)Solving problems and troubleshooting (https://technet.microsoft.com/en-us/library/ee748639(office.14).aspx)

另請參閱See also

概念Concepts

SharePoint Server 2013 的效能測試Performance testing for SharePoint Server 2013

監視和維護 SharePoint Server 2013Monitoring and maintaining SharePoint Server 2013

SharePoint Server 2016 的軟體界限及限制Software boundaries and limits for SharePoint Server 2016

效能及容量測試結果與建議 (SharePoint Server 2013)Performance and capacity test results and recommendations (SharePoint Server 2013)

其他資源Other Resources

Capacity management and sizing overview for SharePoint Server 2013Capacity management and sizing overview for SharePoint Server 2013

效能和容量技術案例研究 (SharePoint Server 2010)Performance and capacity technical case studies (SharePoint Server 2010)