Read http://www.thesanitypoint.com/archive/2009/01/23/sharepoint-and-the-laws-of-physics.aspx to get a reminder that SharePoint needs to be implemented wisely with performance issues in mind. A few notes to glean:
1. Many envision SharePoint as a replacement for their regular network file shares. Keep in mind the "2000 document limit".
2. Even taking appropriate topology and taxonomy steps, heavy file-based SharePoint usage is going to significantly reduce the "rated" capacity of a SharePoint environment.
3. Consider if the users are geographically spread out. Would you want to channel all of the current file-server usage in your remote offices through a single WAN link?
4. Remember that SharePoint itself resides on a Windows server, and stores everything in SQL Server databases, and consider what an all-out consolidation would mean.
5. Don't forget that SharePoint is only one piece of the total puzzle. Your network, your geographical distribution, and other factors, need to play as large a role in your planning for SharePoint as they do with any other system in your enterprise.
6. Read http://technet.microsoft.com/en-us/library/cc261716.aspx for Microsoft's document on MOSS performance/capacity planning.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment