This section provides the capacity specification for the Avaya certified deployment scenarios. Avaya has used these values as a benchmark for capacity verification.

Key considerations:

• The standard storage capacity of a context is 2 KB in raw JSON data. Note that the object might be significantly larger when stored in the data grid depending on the complexity of the object. When you enable optional features, which require memory resources, the size of the Context objects, lease time, or throughput must be decreased to achieve the certified performance. Also, when you use the aliasId feature, the 2 KB standard context must be reduced to 1.5 KB to achieve the certified performance level, in terms of throughput and lease time. Enabling the Audit feature also has an impact on Context Store capacity. You must reduce the context size based on the number of audit entries enabled. For more information, see Avaya Context Store Snap-in Developer Guide.

• The maximum latency for Context Store is 300 milliseconds. Latency is the time interval between the client request and the Context Store response in milliseconds.

• Context Store supports a maximum of three aliasIds.

• For production environments which require the Geo-redundancy feature, each cluster must contain two or more Avaya Breeze® platform nodes with 16 GB of memory and 8 cores allocated to each node.

• For production deployments that are not certified for five notification clients, if you increase the number of notification clients to five, the request per second capacity will be reduced to half.

  Note:

  Context Store performance is tested with only one notification client.

For the capacity certified for each Avaya certified deployment, see the Certified Deployments section in Avaya Context Store Snap-in Release Notes.