Windows performance limitations

Question

What are the limits on the amount of data that can be published to the custom category of Windows performance counters?

I understand that there is no hard limit on the number of counters or the number of instances, but there is a memory limit for the entire category. What is this limit?

Is there a limit on the total number or size of all categories of performance counters? What else should be considered when working with a relatively large amount of data that must be published?

To put this in perspective, I need to publish about 50,000 32-bit counter-instance values. I could categorize them differently, depending on what restrictions exist.

I appreciate that performance counters may not be the best solution, but there are reasons for this insanity.

Answer 1

Under what circumstances will you need to publish tens of thousands of counters.

Remember that the tools that read these counters are usually not designed for such massive data sets (although they may be). As a result, it is possible that although you can create such a data set, the tools that read your data will fail in “interesting” ways.

, . 50 000 ? ? 50 000 ?

Answer 2

? , - ? , ?