Microsoft Office Tutorials and References
In Depth Information
a member of the site collections in any way. This also works from the standpoint of denying a
certain user or security group permission; so even if they are added to a site collection within a
web application, they will not be able to make use of the denied permissions. Keep this in mind
as you plan for user accounts and permissions while designing for your web applications and
site collections. For more on users and permissions, see Chapter 12.
Performance Planning
By now you may have made some plans concerning what OS you’d like to have on your
SharePoint Foundation server; what installation option you’ll use; and what accounts, services,
user account mode, and authentication you’ll implement. You may have decided how you’ll
handle Search (such as putting the index files on a separate drive), set up email, manage paths,
and alternate access mapping, and you’ve mapped out the user accounts, permission levels, and
groups you’ll need.
Now you need to determine whether your server is big enough for the job—today and into
the future.
KEEPING UP-TO-DATE
Planning for performance and storage is more an art than a science. And as time passes (and more
people use the most current version of SharePoint), the ideas about the current best method for
performance or storage planning change to suit. So, be sure to check online to see what the most
recent best practice is for planning for SharePoint.
How do you plan for that? There are really two points of concern, performance and
storage. In terms of performance, it’s good for you to determine how many operations per second
(OPS) your server will need to do under normal (or even extreme) loads. (Storage is measured in
input/ouput operations per second, or IOPS, which is a a little different.)
There are probably as many different ways to plan for performance as there are people using
SharePoint, but for a ballpark, general estimate, there is a tried-and-true formula from WSS 3.0 to
help you with your plans. This formula is very simple, but it can give you a good idea of how to
avoid being underpowered in terms of simple user activity.
Essentially, you need to answer the following questions:
1. How many people are supposed to use SharePoint? (Users)
2. What percentage are really going to use it? (Percent active users)
3. How many operations per day do they do on average (how many documents edited, list
entries added, searches done, and so on)? (Operations)
4. How many hours do the users work in SharePoint on an average day? (Work hours)
5. Does an average work day have particular peaks in performance? (Peak factor)
To calculate the operations per second, multiply items 1, 2, 3, and 5 together and then divide
that number by the number of hours those people are going to be working a day by 360,000
(which is 100 percent conversion × 60 minutes per hour × 60 seconds per minute). Altogether,
that will show you how many operations per second your server needs to efficiently handle.
 
Search JabSto ::




Custom Search