Windows SharePoint Services 3.0 & Site Creation

[pwomack]

We are planning to deploy Windows SharePoint Services 3.0 as a standalone server and will use the MS recommended hardware. We will use SharePoint primarily to manage ~5,000 documents in document libraries, and expect ~1,000 viewings of documents per day. Most of the other SharePoint features will be unavailable to the user.

We want to create 10 sites total (or 9 sub sites under the main site). My question is: Does the number of total sites (in our case 10) effect system performance? That is, response time? Does anyone see a problem here?

Thanks.

 

[MaxEd]

Recommended database size is 2GB so if it's just for viewing and no updates 9 sub sites wouldn't matter much. If you use sharepoint attributes in the lists to identify the files then it's not a problem but if you start thinking sharepoint as your windows boxes where you have so many sub folders you going to have problems and more errors will start creeping up.

-Laughter works miracles.

 

[pwomack]

Thanks, MaxEd. Our libraries will be used only for viewing. We'll have probably 2 contributors, the rest visitors.

I've never come across any documentation that states a 2GB recommended database size. Our total database size will likely be more than double the 2GB size.

 

[Chance1234]

any use

[taken from Mastering Windows Sharepoint 3.0 C.A Callahan]


Performance Planning

Formula

Users X Usage X operations X Peak /(360000 X workhours)

Example

Users:1000
Percentage active usage:60
Operations: 50(per person per page)
Work Hours: 9
Peak Factor: 4

1000 X 60 X 50 X 4 /(360,000 x 9)

This will give the total number of operations per second that your server needs to deliver to your users , in the example 3.7 OPS

a set up of 2.5 GHZ and 1GB ram shoudl eb able to handle at least 10 OPS)








Chance,

F, G + 3MSTG

 

[pwomack]

Thanks, Chance. Very helpful information.