Basic Aspire has a fairly small footprint. For evaluation purposes, it can run on your laptop. For most production implementations, we recommend:
This value does not include logs or data generated due crawls or other component activity
What you need to run Aspire optimally in a complex, enterprise production environment depends on multiple factors, including:
If you need assistance in sizing an Aspire Enterprise system, please contact your Search Technologies Account representative (we'd be happy to help).
Aspire makes substantial use of Maven, in both the build and execution phase. During the build process, Maven will download bundles (jar files) and plugins from several Maven repositories located on the internet (including, but not limited to https://repository.searchtechnologies.com/artifactory/public and http://repo1.maven.org/maven2). During execution, Aspire will download applications and components (OSGI bundles or jar files) from https://repository.searchtechnologies.com/artifactory/public.
Another network consideration is the speed of the network between the content repository and the Aspire server. When an initial crawl or incremental crawl is performed it is typically fetching the entire document and associated metadata. Although the text of each document may be rather small, the full binary can be quite large and if the actual network speed, particularly for WANs, is slow, the overall performance of the system will be slow. There are solution architectures that can be employed to address this situation. Please contact Search Technologies and we would be happy to discuss these issues and potential solutions.