A lot of times in my job, we get alerts for processor usage spikes and memory being below threshold for normal server usage. When these would occur on SharePoint servers, I would go through finding out what processes were running that were using a lot of processor and memory. Turns out that it was usually noderunner.exe that was causing the issue which has to deal with the crawl function of the SharePoint data being indexed by the servers in the farm. So, after looking around on a few sites, I compiled the following ps1 script that can be run on a SharePoint server to get the Crawling status of all the SharePoint Content Sites and how long it took to crawl during the prior cycle:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | Add-PSSnapin microsoft.sharepoint.powershell $ssa = Get-SPEnterpriseSearchServiceApplication | Where-Object { $_.Name -like "*Search*" } $sources = Get-SPEnterpriseSearchCrawlContentSource -SearchApplication $ssa ForEach ($source in $sources) { $log = New-Object Microsoft.Office.Server.Search.Administration.CrawlLog $ssa $last = $log.GetCrawlHistory(1, $source.Id)[0] if ($source.CrawlStatus -ne "Idle") { Write-Host "Content Source $($source.Name) - Crawl In Progress:" ((Get-Date) - $source.CrawlStarted) -ForegroundColor Yellow } else {Write-Host "$($source.Name) Crawl is now Idle" -ForegroundColor Green } if ($last.CrawlDuration.Hours -ge 2) { Write-Host "Content Source $($source.Name): last crawl took over 3 hours!" -ForegroundColor Red } else {Write-Host "The $($source.Name) Crawl took less than 3 hours last time." -ForegroundColor Green } } |
It will output:
– The name of the Content Site being Crawled
– Whether or not the crawl is idle
– If idle, when the crawl started
– If the last crawl took three hours or less
I hope this will give some help to those deep diving into SharePoint Performance.
