0

We are building our new fast farm and have plans to put up one column of Physical servers for FAST indexing and crawling. We will be crawling around 15 million items including SharePoint sites, exchange public folders, custom sql databases and file share documents. I know if it was just SharePoint sites, the formula is 20% of your total content DB size. Is there some similar formula with which I can calculate the physical memory required on my index and crawl boxes. As per MS (http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23576) they recommend to use 1 TB HDD size per 5 million items. But that doesn't seems to be the case. Any recommendations?

0

As data vary so much from installation to installation your best approach is to index perhaps 100,000 items which are representative of your corpus, and extrapolate the disk needed from that.

Also read over the scenario listed at http://technet.microsoft.com/en-us/library/ff599526.aspx which have numbers for raw data and index size, which might can carry over to your installation.

  • Thnaks for the link and info. So that test results are somewhat in-line with what MS recommends, 1 TB HDD for every million items. However as far as I know there is a concept in FAST that the items index gets cached on WFE's for faster retrieval. Is there a formula or calculation by which we can calculate HDD requirements on WFE if its just gonna host FAST search site? – Ashish Mar 13 '12 at 20:26
  • 1
    No caching on the WFE's. The crawler meta data is stored in the crawler db, but 1/5 or so of what SP search stores there. The rest is stored on the FAST servers. – Mikael Svenson Mar 14 '12 at 10:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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