sippy / rtpproxy

The RTPproxy is a high-performance software proxy for RTP streams that can work together with Sippy B2BUA, Kamailio, OpenSIPS and SER.
http://rtpproxy.org
BSD 2-Clause "Simplified" License
405 stars 114 forks source link

What is the memory and CPU requirements for RTPProxy #145

Open SiirRandall opened 1 year ago

SiirRandall commented 1 year ago

Hello,

We would like to know what is the most optimal settings for a large-scale deployment. We have 350,000 calls a day. We use VMs for our RTPProxy. We would like to use the maximum settings we can for each RTPProxy instance. I looked at your manual on your website but I do not see any information your website. Thank you for your time.

sobomax commented 1 year ago

Hi there, the requirements for the memory is very small. Single rtpproxy process won't be using more than 100-200MB of RAM. With regards to the number of sessions, you need to have one rtpproxy instance per about 1,000 simultaneous calls and it will be using some 2.5 CPU cores at that load level. So it's the question of how those 350,000 calls a day are distributed across the time. If it's conversational traffic then 1.5 million calls a day correspond to roughly some 2,000 sessions at peak time, hence if your traffic is like that then you won't need more than 1 instance and it would be using resources equivalent to a single CPU core. Hope it helps!