PreEmptive Analytics Standalone Repository User Guide

System Requirements

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:

  • CPU: 64-bit, 2 cores, 2.0 GHz each
  • RAM: 3.5 GB
  • Disk: See below
  • OS: 64-bit version of one of the following:
    • Windows Server 2012, or 2012 R2 (recommended)
    • Windows Server 2008 R2
    • Windows 8.1
    • Windows 7

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:

  • Internet Information Services (IIS): 7.5 or 8.0
    • Static Content
    • IIS Management Console
  • .NET Framework 4.5
    • ASP .NET 4.5

The Repository requires MongoDB 2.6.10 or greater, which should be installed according to the instructions in the MongoBD Installation section.

Disk space planning

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.)

Estimating network envelope volume

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:

  • A "typical" application generates transmissions that average about 4KB each.
  • We have observed that the vast majority of applications report (far) fewer than 1 transmission per second (across all users/instances of the application).
  • At that rate (one 4KB transmission per second), a Repository will consume 138 GiB in the first year, and an additional 132 GiB each year thereafter.

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.



Standalone Repository Version 1.1.0. Copyright © 2015 PreEmptive Solutions, LLC