Scaling guidelines for NFM-P XML API clients
XML-API client limits
There can be a maximum of 20 NFM-P XML API JMS clients. Greater than 10 NFM-P XML API JMS clients requires an NFM-P server with a minimum of 16 CPU Cores.
The number of NFM-P XML API HTTP clients supported by an NFM-P server station is 2 times the number of CPU cores with at least 10 and at most 30 clients supported.
The maximum number of concurrent findToFile operations supported is five. The maximum number of concurrent control script executions is five.
XML API JMS client messaging rates
Network latency between the NFM-P server and an NFM-P XML API client will reduce the JMS message rate. For durable JMS clients, the Duplicate OK method will allow for a higher message rate than the Auto Acknowledge method. See the NSP NFM-P XML API Developer Guide for more information.
NFM-P is also able to deliver hundreds of messages per second to a non-durable NFM-P XML API client.
Table 5-15: JMS durable messaging rates
|
JMS messaging |
Round-trip latency from the XML API client to the NFM-P server | ||
|---|---|---|---|
|
0 ms |
20 ms |
40 ms | |
|
Durable connection with Auto-acknowledge (messages/s) |
1000 |
692 |
349 |
|
Durable connection with Duplicates-OK (messages/s) |
1000 |
693 |
347 |