ReadPropertyMultiple Requests Statistic

There is a counter at the service level for each ReadPropertyMultiple request sent and there is also a counter within the cache module, which increments when a cache property is updated by the ReadPropertyMultiple service. The difference between the two counters is that the first reports the number for service requests, while the second reports the number of items updated by the service.

For example, if the ReadPropertyMultiple service is used by the cache to update 100 properties within the cache, then the counter at the service level increments by 1 and the counter in the cache increments by 100 (1 for each property within the service).

As for the totals, it depends on the frequency that it is polling, as well as the quantity.

If the poll rate is 5 seconds and the number of items in a ReadPropertyMultiple request is 50, then the following is expected:

For each item, the number of polls per week needs to be (60 * 60 * 24 * 7)/5 = 18,000

The number of ReadPropertyMultiple requests depends on the maximum number of items allowed in each request.

If you have 100,000 points and the maximum is 50 per request, then, for each poll (every 5 seconds), 2,000 requests are required.

This would mean 18,000 * 2,000 = 36,000,000 Read Property Multiple requests are required.

That corresponds to 50 * 36,000,0000 = 1,800,000,000 property updates within the cache by Read Property Multiple requests.

There are hourly, daily and weekly totals that reset at the end of the period. There is also a running total which is never reset back to zero.

It's important to know what values are reported for all of the counters (hourly, daily, weekly) and the running total. The last day, hour and week are the ones that we could use to verify that the numbers are correct.