The Standalone Repository is typically installed side-by-side with a PreEmptive Analytics Replayer. The specifications below are the minimum required for a host with both the Repository and the Replayer installed.
The Repository and Replayer require the following minimum system resources:
Note that the upper limit for the rate at which the Repository can accept envelopes is typically CPU-bound. A host configured as above will typically be able to sustain ~300 inbound envelopes per second. This is far more than should be needed for most deployments, but the extra CPU overhead is required for Replayer use. The Replayer is typically CPU-bound as well, so the overall CPU allocation will typically determine the maximum possible replay rate.
The Repository also depends on the following Windows features, which must be installed in this order:
The Repository requires MongoDB 2.6.10 or greater, which should be installed according to the instructions in the MongoBD Installation section.
In terms of disk usage, the Repository will typically consume, in storage, approximately 110% of the number of bytes that it receives over the network, plus a static 6 GiB for MongoDB overhead. For example, if the Repository receives 10 GiB of envelope data over the wire, it will typically consume 17 GiB of disk. (But 100 GiB over the wire results in only 117 GiB of disk.)
Determining the actual disk usage for a particular installation requires estimating the average incoming envelope rate and average incoming envelope size, both of which can be hard to predict. Before getting into details, consider this example:
To perform your own detailed estimate of disk usage, please refer to the System Requirements section of the Workbench documentation which includes details about estimating incoming envelope rate, incoming envelope size, and large data issues. It will provide the necessary context for you to estimate your incoming envelope volume, from which you can quickly calculate Repository disk usage.