search

sipcapture / heplify

Portable and Lightweight HEP Capture Agent for HOMER
https://sipcapture.org
GNU Affero General Public License v3.0
179 stars 64 forks source link

Sizing #294

Closed abitrusty closed 4 days ago

abitrusty commented 4 days ago

Hi - don't have an issue but is there any information on agent sizing.

Can an Heplify agent running on a Linux server with 1 x vCPU and 4GB handle 100Mb of concurrent Voip traffic easily?

Any info appreciated?

lmangani commented 4 days ago

When talking about "vCPU" and without any real details this type of question is impossible to answer. The real issue is usually the network and not the agent. Try it out and let us know if you experience issues.

abitrusty commented 4 days ago

hi thanks for reply. I don't have any specifics as haven't deployed anything yet but am wondering what (if any) capacity issues i might hit. Each heplify agent might be receiving over 100Mbps of sustained spanned SIP/RTP traffic. Are there any considerations I need to make in regards to the underlying linux VM to support this amount of traffic

lmangani commented 4 days ago

With 100Mbps of traffic you should see no issues. If the processing will max out the CPU you will simply need to scale up as It all depends on the complexity of the underlying traffic being captured, reassembled, dissected, extracted, correlated, etc. Each VM setup is different - some do great, some do not. Always watch for kernel drops and prefer TCP delivery for HEP packets.