Considering Performance and Scalability

With the increased number of configuration and service databases in SharePoint 2010, it is recommended that administrators thoroughly test the hardware capabilities of their SQL servers for performance and scalability issues when creating database mirroring sessions. Although Microsoft has stated that the practical maximum number of mirrored databases should not exceed 50, this number will vary depending on the following factors:

Network latency— It is recommended that network latency between the principal server and mirror server not exceed 1ms. This applies to synchronous mirroring only.

Network bandwidth— It is recommended that the network bandwidth between the principal server and mirror server be at 1Gb per second and less than 1ms of latency for synchronous mirroring. Asynchronous mirroring does not have these same requirements, but does require sufficient bandwidth to handle the flow of data from principal to mirror.

Memory— The amount of memory on both the principal server and mirror server should follow the hardware recommendations for deploying a SharePoint 2010 farm.

Processing power— Two threads are created for each database mirroring session; therefore, sufficient processing power is necessary on both the principal and mirror server to handle each database mirroring session without severely effecting performance.

Disk I/O— Because database mirroring involves writing potentially large amounts of logs to disk, it is recommended that disk I/O is optimized for faster disk access.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset