3. WHAT HAPPENED TO FAST?FAST was a true Enterprise Search platform, so…
4. The evolution of FASTFDS ESPFSISFSIAFS4SPSearch inSP2013Search inSP2010Secret sauce(incl. Mars)
5. End of an era, birth of a New age• FAST now “fully integrated” into SP2013– True, but there’s more!• No longer a “FAST license”– SP2013 contains everything– Enterprise version1997 – 2013
6. Empoweringthe wholeSharePointexperienceBetter, morepowerfulextensibilityMajor userexperienceoverhaulMain themes of the new Search• User Experience is finally a key componentVastlyimprovedsearch coreFinally asingle searcharchitecture
7. User Experience is finally key• Revamped user/admin interface• Hover panels, previews• Query rules, result blocks• Result types, display templates• “You’ve seen this result before”• Query Builder• Content Search web part• Etc.
8. For the first time,Search isn’t defined by thenuts and bolts,but from the User Experienceand high-level tools around it.
9. SHAREPOINT 2013’sSEARCH EXPERIENCEExamining
10. The search center
11. Build and extend• With the new Content Search Web part (CSWP)• With the new REST APIs
12. NEW SEARCH ARCHITECTUREExamining SharePoint 2013’s
13. Search architecturePublic APIUnit of scale/role boundaryExtensibility PointsCrawlAdminLinkAnalyticsReporting
14. The search components• A “node” is an instance of a component• Scale by adding nodes
16. The new Search Service Application
17. Keeping it all togetherServices ProcessesProcess name Descriptionhostcontrollerservice.exe Process controller. Monitors and restarts children.noderunner.exe A search component (except the crawl component)mssearch.exe The crawl component.
18. Crawl component• Changes from SP2010– Improved performance– Continuous crawl• Improves freshness– Crawl Log• More details• Document removal– Crawl Health Report• Huge improvement!Crawlmssearch.exe
19. Continuous crawls• Not event-driven indexing• Starts crawl regardless of prior crawl session• Large change sets no longer bad for freshness• Only available for SharePoint content types– Possible to crawl SP 2010 and 2007timeContinuousFull andincrementalDefault 15 min
20. Crawl health reportsRate Latency FreshnessCPU andmemoryloadContentProcessingactivityEtc.Crawl rate per type Crawl load
21. Content processing component• Schema mapping– Crawled Managedproperties• Entity extraction– Companies and custom• Advanced Filter Pack is gone– PDFs are out of the box• Extensible through web service• Internally: processing flows– Replaces Python pipelineLink
22. Processing flow execution
23. Index component• Propriety disk-based index• Discrete portions calledpartitions• 1 partition per 10M docs• Each partition contains 1+replicas for fault-toleranceand query volume• 1 replica, 1 server• All servers perform indexing(partially in-memory)
24. Example: Partitions and replicasSame contentDifferent content
25. Query processing component• Prepares the queries– Query rules– Result sources– Linguistics/dictionaries– Etc.• Manipulates the results– Display templates– Late security trimming– Etc.• Internally: processing flows– No custom processing as in Content Processing– Still MAJOR improvement
26. Query rules• For a certain term trigger certain action:– Add/change query terms– Use alternate sorting/relevance– Hybrid search (or other federated results)– Etc.• Replaces search keywords in SP2010• Configure at farm, site collection or site-level
27. Query builder• Easily builds KQL– CSWP, result sources, query rules, etc.
28. Query client types• Adjust throttling per client type
29. Query health reportsTrend OverallLatency inmain flowLatency ineachsubflowIndex times Etc.Latency per processing node in SharePoint flow
30. Analytics processing component• Analyzes crawled items and search usage• Updates index without re-indexing documents• Result: relevance becomes self-learning– Also: search reports and recommendationsLinkAnalyticsReporting
31. Search reports• Self-learning relevance aside,never underestimate manual effort!– Query rules, synonyms, boosts, etc.• Automatic reports:– Number of queries– Top queries– Abandoned queries– No-result queries– Query rule usage
32. Search administration component• Provisions other search components• Talks to Admin database on behalf of:Crawl, Content and Query processingcomponents• In previous FAST products, it was hard to makethe admin component redundant– Not the case in SP2013!– Scale appropriatelyAdmin
33. Hardware properties• Highlights– In-memory technology– VMs now supported for production– SANs less problematicComponent CPU Memory Disk I/O NetworkCrawl Medium Medium Medium HighContent processing High High MediumIndex High High High MediumQuery processing Low Medium MediumAnalytics processing Medium Medium Medium HighSearch administration Low Low Low Low
34. Questions?Håll utkik på vår blogg!blog.comperiosearch.comEmail: firstname.lastname@example.orgTwitter: @marcjohaBlog: http://blog.comperiosearch.comLinkedIn: http://www.linkedin.com/in/marcusjohansson