---
title: "Operations per Minute"
slug: "guide/configuration/server-start-up-file/operations-per-minute"
sidebar:
  order: 24
---

<a id="ref-140af51d8fed"></a>
<a id="ref-c2ea2e3be7ab"></a>
<a id="ref-9307a09c0d2c"></a>

## Synopsis

`egr.eai.server.operations_per_minute=<ops-per-min>`

**Default Value:** `unlimited`

The value of this option must be either a positive integer or the string `unlimited`[^1].

For the purpose of licensing, the number of non-trivial state-changing operations per minute the Online Configurator is able to serve is limited. The number of operations per minute specified with this option may further be reduced during start-up due to insufficient availability of throughput license features (§[Feature egr.eai.server.throughput](/pCon/configuratorOnline/specs/guide/licensing/license-features/feature-egr-eai-server-throughput#ref-e5f612c1f03a)).

**Informational:** The current algorithm used to limit the number of operations per minute works as follows (although the implementation is quite different): Assuming *n* is the number of operations per minute, there is a blocking queue of tickets with a maximum size of *n*. One thread inserts a ticket at the end of the queue every *60 / n* seconds, blocking if the queue is full. Threads servicing operations take a ticket from the front of the queue before they start one of the operations in question, blocking if necessary until a ticket becomes available. If more than one thread is waiting for a ticket to become available, then the longest waiting thread gets the next ticket that becomes available.

[^1]: Prior to version 2.0 RC 2, there was no default for this option (i.e. it always had to be specified in the start-up file), and the special value `unlimited` was not supported.
