SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm about to start a project using the FAST Search Server and would like to know something about how we can scale the Search Server.

Can we setup multiple search server application pools or how does this work?


share|improve this question
As 2013 is around the corner I would reconsider going for FS4SP, and perhaps set up a 2013 farm doing the indexing instead. Certainly not more work, and more future proof. – Mikael Svenson Oct 4 '12 at 7:58
Thanks, and that's actually what we are aiming for. About 80% of the new search of SharePoint 2013 is FAST hence we need to think fast when scaling SharePoint Search in the feature :) – Eric Herlitz Oct 5 '12 at 7:20
up vote 1 down vote accepted

With FAST Search you are going to have a separate set of servers dedicated to document processing, indexing and other components. The configuration options are very flexible so you'll need to come up with the proper architecture based on your specific requirements for content freshness, query throughput, index size and redundancy. Your SharePoint application servers will only be responsible for crawling SharePoint sites. The topic is too broad for a short answer like this but there's plenty of information available on TechNet. Here's a good starting point: Plan search topology (FAST Search Server 2010 for SharePoint)

share|improve this answer
Thanks, I'll start there! – Eric Herlitz Oct 3 '12 at 18:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.