Hardware and Network Considerations
For Information on Aspire 3.1 Click Here
Basic Aspire has a fairly small footprint. For evaluation purposes, it can run on your laptop. For most production implementations, we recommend:
- A 4-core server running 64-bit Linux or Windows
- At least 4GB of RAM
- Minimal disk (Aspire itself currently runs in less than 100MB)
- Network connection speed of 100Mbps minimum, and preferred 1Gbps
What you need to run Aspire optimally in a complex, enterprise production environment depends on multiple factors, including:
- The total number of data sources to be crawled, and for each data source:
- What type of repository holds the data (i.e. SharePoint, Documentum, RDBMS, etc.)
- Total number of documents
- Total number of bytes
- How long an initial indexing crawl should take
- How long a periodic incremental indexing crawl should take
- Are real-time updates required?
- Network speed between repository and Aspire server
- Data metrics for query client connections:
- Number of client connections expected
- Number of queries per second expected
- Query latency times required / expected
- Is authentication, authorization, and group expansion required for client search requests?
- Will distributed processing be required?
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 http://repository.searchtechnologies.com:8081/artifactory/simple/community-public and http://repo1.maven.org/maven2). During execution, Aspire will download applications and components (OSGI bundles or jar files) from http://repository.searchtechnologies.com:8081/artifactory/simple/community-public.
If allowing Aspire access to the internet is not in line with your network policy, see Creating Distributions for Machines with No Internet Access or Using your own Maven repository with Aspire.
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.