Unique Permission on every individual item in a SharePoint Form Library can result in very slow performance ???
Hi All, I just want to know that can sharePoint performance become slow by assigning unique permission on every individual item ? I have a form library in which there are hundreds of items and every item has unique permissions. FYI: I read the following blogs and they are of the opinion that SharePoint performance can become horribly slow by assigning unique permissions URL 1: http://sharepointbergen.blogspot.com/2008/09/sharepoint-2007-item-level-security.html URL 2: http://weblogs.asp.net/erobillard/archive/2008/09/11/sharepoint-security-hard-limits-and-recommended-practices.aspx Any help in this regard will be greatly appreciated.. Regards.. Muhammad Tariq khan
October 19th, 2010 9:38am
Hi, How many users and how many list items per list are you thinking will have unique item level permissions? The second article is relevant and as noted the issues were resolved in SP1. Howver, large lists where views have not been created to keep the rendering of items to less than 2000 will render more slowly than lists where views have been created to keep the rendering of list items to a smaller number. We use list item permissions on sensitive information all the time like an expense report submission for approval, until the item is moved to the AP Expense library we give the owner and thye approvers permission to the item. Once its approved, and paid we move it to a document library where only AP has user rights.. I think a larger issues by far will be your SQL performance and whether you have followed best practices for your SQL deployment (IOPs, LUNs, spindles, high performance db files, db location, db size, volume size, memory, and processor, and performing routine maintenance) one example and probably not the best Hawaiian Airlines http://www.hawaiianairlines.com uses SharePoint to manage its public facing site and there are many Access restrictions.. I have a client with 16k users, 5k concurrent users, 63 content dbs, 1tb of content, 1.43mb site homepage size, and they are getting sub 2 second page load times from within the corporate headquarters. The issue we have are global deployments and the limited choices available for follow the sun deplyments... Deploying any application is a balance of resources.... -Ivan Ivan Sanders My LinkedIn Profile, My Blog, @iasanders.
October 19th, 2010 12:18pm
Dear Ivan, My list contains almost 650 items which are growing at a higher speed. All items have unique permission due to security. My total users are 250. And my content DB size is almost 27 GB. I am suffering from very slow SharePoint performance. Can you suggest us any performance tweaking tips or can you propose server/hardware specifications for our environment? FYI: I am using SharePoint Enterprise 2007 updated with SP 2 updated along with SQL Server 2005. Web Front End and SQL Server are on separate machines. Normally we are using SharePoint for Content Management and Web Based InforPath Forms Regards.. Muhammad Tariq khan
October 19th, 2010 3:31pm
Hi Muhammad, The number of users and size of the Dbs are important in the way they relate to the HW you have deployed. Are your running x64, how much memory, how many processors on the App, WFE and SQL servers. In general based on the number of users and size of the content_db I would say that you should be running x64 with 8GB of RAM on your servers, 16GB on SQL if possible. Please provide an example of the types of unique permissions in other words are you breaking inheritance and removing all of the permissions or when you break inheritance do you copy the permissions. The rule is A single list should not have more than 2,000 items per list view. A view or container represents the root of the list, as well as any folders within the list; a folder is a container because other list items are stored within it. Lists can contain millions of items and performance will not be adversely affected as long as you contain your items in views an or folders that do not exceed 2000 items SQL IO is the single issue I find in the field affecting SharePoint performance and I have included a few references on building a Scalable SharePoint environment and SQL maintenance below. SQL Server 2005 SP2 is needed if using the DB maintenance wizard (KB930887). · Physical Volume File Fragmentation: o Defragment your physical volumes on a regular schedule for increased performance! o LUN’s need to be 20-50% larger than the data stored on them allow for effective defragmentation of the data files. · Performance Monitor Counters to watch: o Average Disk Queue Length o Single Digit values are optimal. o Occasional double-digit values aren’t a large concern. o Sustained triple-digit values require attention. · Database Volumes o Separate database volumes into unique LUN’s consisting of unique physical disk spindles. o Prioritize data among faster disks with ranking: o SQL TempDB data files o Database transaction log files o Search database o Content databases · In a heavily read-oriented portal site, prioritize data over logs. · Separate out Search database transaction log from content database transaction logs. · Disk Drive Speed o 15K RPM recommended. Reference Database Maintenance for SharePoint Bill Baer http://go.microsoft.com/fwlink/?LinkId=111531&clcid=0x409 Working with large lists in Office SharePoint Server 2007 Steve Peschka) http://go.microsoft.com/fwlink/?LinkId=95450 Scaling SharePoint 2007 Storage Architecture (R2) Russ Houberg http://www.houberg.net/ -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.
October 21st, 2010 12:15pm
Dear Ivan Sanders, My sharepoint environment is 32 bit. I am using 2 machine (one is sharepoint front end and other one is back-end(DB)). Following are the machine configuration SharePoint Web Front End Machine Specifications Web Front End Processor: Intel(R) Xeon(TM) CPU 3.06GHz (4CPUs), ~3.1 GHz Ram: 3 GB SharePoint Database Machine Specification Web Front End Processor: Intel(R) Xeon(TM) CPU 2.8GHz (4CPUs) Ram: 4 GB FYI: I have updated my SQL Server 2005 Enterprise with Service Pack 3 Now as you suggested in general should we go with x64bit environment with 8GB of RAM on your servers, 16GB on SQL ? Muhammad Tariq khan
October 21st, 2010 12:34pm
Information strcuture should be designed in a way that item level permssions are minimal or none. It could be done by creating multiple document libraries and setting up permissions at that level. Since items are growing at fast pace; hence even after good hardware problem will re-occur.
October 21st, 2010 2:29pm