16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

214 Part III: Planning <strong>and</strong> Deployment<br />

operations per second. Therefore, each server in the farm should be approximately<br />

a 2 x 2-GHz Pentium 4 Server with 2 GB of RAM. This is a close estimate of the hardware<br />

requirements needed for the example. If more portal sites are being hosted on<br />

the same farm, higher hardware requirements are necessary.<br />

Rough hardware estimates are based significantly on the type of farm being<br />

used. Because each farm type has resources broken down in different ways, they<br />

have different operations-per-second estimates. A single server farm with MSDE<br />

cannot exceed five concurrent database jobs, <strong>and</strong> therefore, cannot realistically<br />

exceed five operations per second. For cached operations, a slightly higher operations-per-second<br />

rate might be achieved, but on average, it will remain about five<br />

operations per second. A single server farm with SQL Server will be able to support<br />

around 6 to 7 operations per second for each 1 GHz of processing speed. If the<br />

server is constantly doing a lot of indexing, this number will be lower, as the server<br />

will be using processing resources on indexing.<br />

A small server farm environment will be able to support approximately 7 to 8<br />

operations per second per 1 GHz of processing speed. Again, if there is a lot of indexing,<br />

the number will be lower. You should restrict indexing activities to periods of light<br />

usage, such as late at night, in single-server <strong>and</strong> small server farm environments.<br />

Medium server farm environment can h<strong>and</strong>le more requests, not only because<br />

resource-intensive operations such as indexing are offloaded, but because a<br />

medium server farm can support more than one front-end server. It is the front-end<br />

Web servers <strong>and</strong> search servers that mainly affect the number of operations per second<br />

for users. A medium server farm can support approximately 9 to 10 operations<br />

per second per 1 GHz of processing speed on the front-end Web servers.<br />

Large server farms can h<strong>and</strong>le more requests still because the search <strong>and</strong> Web<br />

components are running on different servers. It’s difficult to estimate the capacity of<br />

large server farms without knowing the breakdown of search requests versus normal<br />

requests. A rough estimate is that a large server farm can support 11 to 12 operations<br />

per second for each 1 GHz of processing power on the front-end Web servers, but<br />

this is a general approximation.<br />

The numbers provided in this section are general guidelines <strong>and</strong> approximations,<br />

as actual results will vary based on the exact hardware you are running. It is<br />

important to run capacity planning tests on your servers to ensure they will be able<br />

to perform adequately. This testing is especially important in a large server farm<br />

environment, where it is harder to gauge the actual hardware requirements without<br />

knowing the exact environment specifications. For example, if there will be a lot of<br />

searching going on in a large server farm, it is important to have many search servers<br />

<strong>and</strong> to test the whole farm using a script that simulates many searches. Full coverage<br />

of testing servers for capacity will be provided in the “Testing for Capacity” section<br />

later in this chapter.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!