Feature egr.eai.server.throughput
This feature has an attribute named operations_per_minute whose value is a positive integer specifying the allowed number of non-trivial state-changing web service operations1 per minute. When the Online Configurator is starting up it tries to lease one or more instances of this feature to meet the required number of operations per minute as configured in the server start-up file (§Operations per Minute). To do so it first fetches all available throughput features, sorts them in descending order according to the number of operations per minute, iterates over the resulting list and leases the current feature if its number of operations per minute is less than or equal to the remaining number of required operations per minute. This approach has two important implications:
-
A throughput feature will always be ignored if it supports more operations per minute than configured in the server start-up file. Thus, if the server is configured to support 200 operations per minute, but the only available throughput feature supports 500 operations per minute, the Online Configurator will fail to start as it would be unable to process any non-trivial state-changing web service operation.
-
The operations per minute provided by a single throughput feature cannot be split between multiple instances of the Online Configurator. For instance, if there were three throughput features available, each providing 100 operations per minute, and two instances of the Online Configurator, each configured to process 150 operations per minute, the allowed throughput of each instance of the Online Configurator would be reduced to 100 operations per minute.
Note: Given these implications, one could be tempted to define license templates with many instances of the throughput feature, each one allowing a single operation per minute. This would be a bad idea, however, as leasing a single instance of a license feature requires a round trip to the license server, and such an approach could severely affect the start-up time of the Online Configurator (in the order of a second or so). So each instance of the throughput feature should probably allow at least 10 operations per minute, a smaller value being of questionable use anyway.
If the number of allowed operations per minute had to be reduced during start-up due to insufficient throughput features then it will not ever be raised again for the current instance of the Online Configurator even if more instances of the throughput feature become available.
Example:
FEATURE egr.eai.server.throughput 1.0 0000-00-00 10 operations_per_minute=100
The example above provides 10 instances of the throughput feature, and each instance allows 100 operations per minute, so in total this example allows 1000 operations per minute.
Footnotes
-
Right now these are the
insertOCDArticleandsetPropertyValueoperations of theBasketService. ↩