locked
FSIS Deployment Planning guide RRS feed

  • Question

  • Hi,

    Does anyone has documentation about sizing hardware requirements for a FSIS projects, specially for IMS and CTS Modules? How can I calculate how many servers do I will require for CTS | IMS modules in a project?

    Thanks for your help,

     

    Félix

     

    Wednesday, February 9, 2011 6:43 PM

Answers

  • Hi Felix,

     

    Sizing guidance is always difficult as it depends significantly on your usage scenarios, but I can provide some basic information that can help you regarding FSIS.

     

    Every FSIS installation needs to have at least one admin node.  For cases where fault tolerance is needed, you will need 3 admin nodes running on separate servers.  The admin nodes are not significant resource hogs - by default they are configured to use a maximum of 512 MB of memory, and we don't anticipate that this will need to be changed.  It is possible to continue using IMS and CTS if the admin node goes down, but if you are using the WDM (part of the UI toolkit) you would need to reconfigure your web.config to contact the IMS nodes directly rather than get their information from the admin node.

     

    IMS requirements depend largely on the size of the context object you are retrieving and whether your are doing federation.  If you are using simple flows where you only query one ESP installation and retrieve a reasonable number of result fields and navigators, an IMS node should not have any problems keeping up with a QR server.  IMS nodes are configured by default to use 800MB of memory max, and that probably won't need to be changed unless you are querying multiple sources and federating the results.  A server should be able to handle 1 IMS node per core, though you should probably reserve a core for the OS.

     

    CTS is the hard one to offer advice on.  The complexity of your flows and the size/type of documents will greatly impact the number of documents that can be processed per second.  That can really only be determined by testing with a representative sample of the documents you will be feeding.  CTS is the most resource intensive process.  --While the default max memory usage for a node is 800MB, you will likely need to increase the limit to at least 2GB and possibly more depending on the flows you will be running.  Since you can mark areas in the flow that can be split into new threads you may not want to run as many CTS nodes on a server as you would for IMS nodes.

     

    Also, we do support running FSIS components on Hyper-V installations, so that can also help you make better use of your hardware. 

     

    I will check to see if any of our architects may be able to provide additional suggestions.

     

    Thanks,

    Patrick


    Patrick Schneider | Microsoft | Enterprise Search Group | Support Escalation Engineer | http://www.microsoft.com/enterprisesearch
    Thursday, February 10, 2011 10:12 AM

All replies

  • Hi Felix,

     

    Sizing guidance is always difficult as it depends significantly on your usage scenarios, but I can provide some basic information that can help you regarding FSIS.

     

    Every FSIS installation needs to have at least one admin node.  For cases where fault tolerance is needed, you will need 3 admin nodes running on separate servers.  The admin nodes are not significant resource hogs - by default they are configured to use a maximum of 512 MB of memory, and we don't anticipate that this will need to be changed.  It is possible to continue using IMS and CTS if the admin node goes down, but if you are using the WDM (part of the UI toolkit) you would need to reconfigure your web.config to contact the IMS nodes directly rather than get their information from the admin node.

     

    IMS requirements depend largely on the size of the context object you are retrieving and whether your are doing federation.  If you are using simple flows where you only query one ESP installation and retrieve a reasonable number of result fields and navigators, an IMS node should not have any problems keeping up with a QR server.  IMS nodes are configured by default to use 800MB of memory max, and that probably won't need to be changed unless you are querying multiple sources and federating the results.  A server should be able to handle 1 IMS node per core, though you should probably reserve a core for the OS.

     

    CTS is the hard one to offer advice on.  The complexity of your flows and the size/type of documents will greatly impact the number of documents that can be processed per second.  That can really only be determined by testing with a representative sample of the documents you will be feeding.  CTS is the most resource intensive process.  --While the default max memory usage for a node is 800MB, you will likely need to increase the limit to at least 2GB and possibly more depending on the flows you will be running.  Since you can mark areas in the flow that can be split into new threads you may not want to run as many CTS nodes on a server as you would for IMS nodes.

     

    Also, we do support running FSIS components on Hyper-V installations, so that can also help you make better use of your hardware. 

     

    I will check to see if any of our architects may be able to provide additional suggestions.

     

    Thanks,

    Patrick


    Patrick Schneider | Microsoft | Enterprise Search Group | Support Escalation Engineer | http://www.microsoft.com/enterprisesearch
    Thursday, February 10, 2011 10:12 AM
  • Thanks Patrick,

    Your answer was very helpfull.  Any more info will be really appreciated.

    -Félix

    • Proposed as answer by Rob Va - MSFT Monday, February 14, 2011 6:52 PM
    Thursday, February 10, 2011 4:17 PM
  • hey hi Patrick,

      where can i get the material like whitepapers,learning links regarding Enterprise Search Platform (ESP),Content Transformation Services (CTS),Content Distributor Emulator(CDE),Interaction Management Services (IMSI),IMS UI Toolkit ,FAST Search Designer for Visual Studio,Search Business Manager

    for learn,practice and deployments

    thanks in advance

    shrikants

    software engineer/Microsoft Technology Specialist /

     


    shrikants
    Wednesday, June 8, 2011 4:07 AM
  • All documentation for ESP and FSIS are available through http://connect.microsoft.com/fastsearch.  Requests for access to this information should go through fastcsrv@microsoft.com

     

    Thanks,

    Patrick

     


    Patrick Schneider | Microsoft | Enterprise Search Group | Support Escalation Engineer | http://www.microsoft.com/enterprisesearch
    Thursday, June 9, 2011 8:26 AM
  • Hi Patrick,

    The documentation that i can found in MS connect comes with the installation files. There are other documentation?

    Thanks,

     

    Felix

    Thursday, June 9, 2011 7:08 PM
  • Hi,

    Just curious why do you need 3 admin nodes for fault-tolerance / redundancy... a Primary and a secondary are not enough?

    Thanks

    Chris


    Thursday, June 16, 2011 3:53 PM
  • Hi Patrick,

    AFAIK there's not any other official documentation that what comes bundled with FSIS (CTS/IMS) and the ESP installers.

    Marcus


    Search Enthusiast

    http://www.comperiosearch.com | http://www.linkedin.com/in/marcusjohansson

    Sunday, June 19, 2011 8:48 PM