I have a small one server SharePoint implementation. I have a full crawl set for Saturday morning. During full crawls, the CPU spikes to above 97% utilization for a very long duration and Alarm Point sends a page to the infrastructure team. Is there any way for me to reduce the impact of search crawls? I have the priority of the crawl set to 'normal' and I have tried multiple times but see the same result.
asked Sep 10, 2012 at 13:45
-
Have you checked the ULS for SPRequest errors? and or any long query errors you are getting? I have a feeling you have some customisation somewhere that is slowing the crawler.– Hugh WoodCommented Sep 10, 2012 at 13:56
-
1To add to what James said, if you have Ifilter setup it can cause this to happen as well.– GenePACommented Sep 10, 2012 at 14:27
-
Thanks. I was not considering the impact of iFilters.– James GrizzleCommented Sep 10, 2012 at 18:08
Add a comment
|
2 Answers
To answer your specific question, yes, there is. Go into Central Administration - Shared Services - Search Administration (or if you are on 2010, Manage the Search Service Application) and there is a link on the left called "Crawler Impact Rules". You can use those to control how hard the crawler hits the site. Bear in mind that reducing the impact will also increase the duration of the crawl, which can be an issue if you have a lot of content
-
Thanks! Additionally, I would like to point out 'Set-SPEnterpriseSearchService -PerformanceLevel "Reduced" ' if anyone comes across this in the future. Commented Sep 10, 2012 at 18:07
Do a incremental crawl instead of a full crawl. You really don't need a full crawl that often and on a small server it will really drag it down. You could change that crawl to be once every few days instead. Another idea is to make sure that the time it runs is the time with the least traffic (not sure of sat morning means 6AM or 1AM)
