Introduction to SharePoint Hardware Selection

Reprinted from: http://www.cnblogs.com/poissonnotes/archive/2010/11/26/1889103.html

In addition to the topology and software boundaries, performance and availability are also affected by hardware limitations and redundancy. This section provides some general suggestions to help you select the right hardware for the server farm. When selecting hardware for optimal performance, consider the following suggestions.

● Purchase 64-bit hardware

Although SharePoint can be deployed on a 32-bit server, we strongly recommend that you select 64-bit hardware and 64-bit windows
Server operating system. This not only improves performance, but also makes it a better choice for the end, because
In the future, Sharepoint only supports 64-bit servers. That is to say, if you decide to upgrade to the next version of SharePoint, the 32-bit hardware will also be decommissioned. In addition, the 64-bit hardware also allows us to add more than 4 GB memory for the server. When selecting 64-bit hardware, the only warning is about the availability of some third-party ifilter 64-bit compilation. 32-bit
Ifilter cannot work on a 64-bit Indexing Server. If you need to rely on one or more 32-bit ifilters
Ifilter does not provide a valid 64-bit version. Therefore, deploy a dedicated 32-bit Index Server.

● Use multi-core processors

Sharepoint is a highly-used multi-threaded application. Web Front-end servers use separate threads to process user requests, and each application pool in IIS (Internet Information Service) is mapped to a separate process. The indexing server uses multiple processes and threads to crawl and index content. Query servers and databases also use a multi-threaded architecture to process concurrent requests. Therefore, avoid using a single-core processor-try to choose a dual-core or quad-core or even more multi-core processor.

 

● Install multi-processor

A multi-processor motherboard should be selected for servers that carry non-redundancy roles. This allows you to expand the Indexing Server and database server to the maximum extent. If you want to minimize the number of servers in the server farm, you can also use multiple processors for redundant server roles such as Web Front-end servers and query servers.

● Large memory usage

It is very important to install enough memory on all servers. Insufficient memory will lead to data exchange between large volumes and slow disks. Taking 4 GB as the starting value of memory is a good work habit.

 

● Use high-speed memory

Ensure that the purchased memory has the fastest bus speed supported by the processor.

● Use high-speed Disks

Deploy the fastest storage device that can be provided to carry data files with a large number of I/0 operations. To achieve optimal performance and reliability, select
SCSI (Small Computer System Interface) drives or SATA (Serial ATA) II drives, Sata II drives are generally cheaper than SCSI drives.

● Use a disk array

Configure multiple disks in a raidio array to improve both performance and availability. If the disk write performance is not important and availability is important, use RAID 5. If the data is frequently modified, consider raid 10, while RAID 5 is used when the data is rarely updated. For example, use RAID 5 for operating system files and raidio for Sharepoint content index files.

● Install a gigabit network

To reduce the waiting time and obtain high bandwidth, a backbone network with a minimum bandwidth of 1 GB should be used to connect the servers in the server farm. Another important factor to improve performance and availability is the isolation of data files with a large number of I/0 operations to their own disks. A disk ingot is equivalent to a disk's read/write head. In any system, the disk is usually the slowest component, and if different applications are forced to compete for the use time of the main axis, the performance bottleneck will soon be exposed. The items listed below will help you understand which areas are worth investing in dedicated disk arrays.

● Database Server

Gradually isolate the database to a separate ingot in the following order: temporary database, transaction processing log, SSP database, content database, and SharePoint configuration database.

● Search Server

The query server and Index Server are the primary users of disk I/0. Therefore, isolating the content index to a separate disk ingot may bring about a big difference.

The recommended hardware installation is certainly not the cheapest solution. Therefore, choosing the right hardware may take into account both business needs and costs. If you finally decide to plan many servers and many dedicated SCSI disk arrays, you can consider deploying a storage area network (SAN) solution in terms of price and maintenance. The San solution is a physically independent server in a network that provides shared storage for other servers. Each server that requires a large amount of high-speed storage is allocated with some shared storage, and software makes these shared storage as local drives on the server. A major benefit of using the San solution is the ability to centrally manage physical drives.

 

Fixed Link: http://www.nbseoer.com/tansuanyinliaohui/732.html