Business Productivity and Information Architecture

SharePoint Tip #15. Do you know “that users in SharePoint groups affect crawling performance”?

Adding users explicitly to SharePoint Groups, instead of adding AD security groups affects how crawling performs.

If you add/remove users from the SharePoint group it will force search to crawl content - "Security only crawl". Incremental crawl starts to update security changes, and all “Updated ACL’s” must be pushed down to all affected items within the index. This process might take a lot of time if changes affect a lot of items in SharePoint and you have big number of users in SharePoint.

Managing users via AD groups won't cause ACL changes, and no security only crawls will occur.

Source

 

Have anything to add?! Send your tips to be published via this form

Posted: Wed, Feb 18 2009 0:02 by Michael | with 2 comment(s)
Filed under:

Comments

Nee Okai said:

Thanks Michael for the tip on AD. I am a newbie to sharepoint. I would like to ask you two questions:

1) How do you list current logon users to a sharepoint site?

2) I am planning to deploy sharepoint 2007/SQL 2005/Windows 2008 on a Hyper_V configuration:

i) SQL Server 2005 will be on separate physical server(single);

ii) Two Web Front End Servers on Hyper-V virtual machines (2G RAM) each;

iii) An index server on another virtual server (4GB RAM).

All virtual machines are running on the same physical server running windows 2008 core server (32GB intial RAM.

Will this configuration be feasible for production in a small company (400 users)?

Thanks for any help.

Nee

email: nokai@atcc.org

# April 8, 2009 10:14 AM

Michael said:

Hello,

1) you just create a new AG group, where you put your "login" users together. The point is that all fine-grained groping happen on the level of AD, not SharePoint. There is nothing bad to put user-by-users inside the SharePoint, but this might be not ideal case for the large farms.

2) "Index on another virtual server" is what I'd be very careful about. It might be ok when you don't have a lot of contend and don't optimize your DB to the specific content. But it might cause you performance issues for the large content. Take into account that index usually takes 10%-30% of you actual content and propagated to the Query servers incrementally. To understand if Index server is suitable to be on the virtual server you need to perform some testing. The good index server crawls and propagates the new part of the index in 3-30 seconds. So, just add new document to the farm, and check if you are able to find this document via SharePoint Search in 30 secs. If not - you Index server hinders from the performance issue (consider using physical HDD first and then move index role to the physical server)

# April 8, 2009 5:11 PM
Leave a Comment

(required) 

(required) 

(optional)
 

(required) 

If you can't read this number refresh your screen
Enter the numbers above: