ping exporter maximum target scaling limitations #98
Description
We've been doing some scaling testing and it appears that with more than 100,000 targets setup that some internal limits are hit that cause ping_exporter to no longer be able to accurately track and export the stats despite there being plenty of local CPU resources (eg, never exceeds 1.5 cores with many available.) Nobody on our end is familiar with go and we're curious what you believe the theoretical and practical limits are for the number of targets in a given single instance of ping_exporter. Do you believe these limits can be increased such that the only limit is network speed and available CPU resources?