Thank you for clarification. I was interested in If there are any 
disadvantages If the amount of CPU cores is too high maybe because of 
Overhead to share the load.

Good to know i can scale it easily If i run it on VMs

Ben Kochie schrieb am Samstag, 13. Januar 2024 um 10:51:49 UTC+1:

> No, Go is not specifically limited to a number of cores. For the 
> exporters, they should scale vertically just fine as well as horizontally.
>
> The only limit I've seen is how well the SNMP exporter's UDP packet 
> handling works. IIRC you may run into UDP packets per second limits before 
> you run into actual CPU limits.
>
> It's not something a lot of people have tested/used in production that 
> scale. At least not enough that I've gotten any good feedback.
>
> On Sat, Jan 13, 2024 at 1:20 AM Alexander Wilke <nachtf...@gmail.com> 
> wrote:
>
>> Hello,
>> sorry to hijack this thread a little bit but Brian talks about "4 CPU 
>> cores" and Ben says "scale horizontally".
>>
>> Just for interest - why not just use 8, 16, or 32 CPU cores? Is Go 
>> limited at a specific CPU amount or is there a disadvantage to have to many 
>> cores?
>> I think if someone is monitoring so many devices this is enterprise 
>> network and servers/VMs with more CPUs are no problem.
>>
>> Ben Kochie schrieb am Freitag, 12. Januar 2024 um 21:50:57 UTC+1:
>>
>>> Those sound like reasonable amounts for those exporters.
>>>
>>> I've heard of people hitting thousands of SNMP devices from the 
>>> snmp_exporter.
>>>
>>> Since the exporters are in Go, they scale well. But if it's not enough, 
>>> the advantage of their design means they can be deployed horizontally. You 
>>> could run several exporters in parallel and use a simple http load balancer 
>>> like Envoy or HAProxy. 
>>>
>>> On Fri, Jan 12, 2024, 02:32 'Elliott Balsley' via Prometheus Users <
>>> promethe...@googlegroups.com> wrote:
>>>
>>>> I'm curious if anyone has experimented to find out how many targets can 
>>>> reasonably be scraped by a single instance of blackbox and snmp exporters. 
>>>>  
>>>> I know Prometheus itself can handle tens of thousands of targets, but I'm 
>>>> wondering at what point it becomes necessary to split up the scraping.  
>>>> I'll find out for myself soon enough, I just wanted to check and see if 
>>>> anyone has tested this already.  I'm thinking I would have around 10K 
>>>> targets for blackbox, and 1K for snmp.
>>>>
>>>> I'm using http_sd_config with a 15 second refresh interval, so that's 
>>>> another potential bottleneck I'll have to test.
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "Prometheus Users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to prometheus-use...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/prometheus-users/CALajkdh7EhHAVN5nJNYqJjKvcH_rfT1L7ZaPvPR4L-xjypKSbg%40mail.gmail.com
>>>>  
>>>> <https://groups.google.com/d/msgid/prometheus-users/CALajkdh7EhHAVN5nJNYqJjKvcH_rfT1L7ZaPvPR4L-xjypKSbg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Prometheus Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to prometheus-use...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/prometheus-users/ae1c9448-82ea-4bf3-b2d8-f620de2444a6n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/prometheus-users/ae1c9448-82ea-4bf3-b2d8-f620de2444a6n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prometheus-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/2dffb8bc-c071-4328-89f8-f60366fad29fn%40googlegroups.com.

Reply via email to