-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
high cpu consumtion for 100 calls #18
Comments
Welcome to GitHub! The authors of Opus Codec have an FAQ for this. (1) The first thing you should double-check: Do you need the bitrate and channels? (2) If that does not help, you are able to play around with the complexity. That can be changed in the file
for example after the code line (3) However, the most reduction is done when no transcoding and just pass-through happens. For this, double-check why both call legs require transcoding at all. If all this did not help, please, look out for a qualified computer scientist who knows about CPU profiling. He is able to identify hot spots and/or peaks in your installation and can provide advice. |
@traud thank you for the response. As I am testing it on load setup with transcoding, playing wav file on opus negotiated channels, with complexity 5 and bitrate auto (-1000) by setting for application VoIP. |
I cannot comment on this because in my setup I have exactly one call in transcoding, at maximum. 100 calls and 3 cores sound reasonable. Nevertheless, I am sure there is room for optimization.
Not sure why you mention the translation cost table. Just to avoid any possible misunderstanding, the values in that table are not absolute but relative. They indicate the best route for the originating audio codec. For example, for Opus Codec, slin is the shortest route. You cannot compare one value for G.711 with a value for Opus Codec. The values are just about to find the best route.
I recommend to play around not with |
for 100 calls it using 3 cores. can we optimize it for the same?
The text was updated successfully, but these errors were encountered: