My optimisation work is nearly complete. According to the GNU profiler (gprof) the encoder is now taking around 2.75 seconds and the decoder around 0.75 seconds for the 37.5 second test vector. Add those together and you get 3.5 seconds, less than 10% of the realtime rate for duplex audio. So, we're probably looking at 10% CPU per full duplex channel.Envoyé par jean
Excluding any other software running, that does mean that on G729a alone a raspberry pi IS just powerful enough to encode/decode 10 full duplex channels!
I still have lots of tidying up to to, and there are a few more areas left to optimise, but there is not much fat left to trim. It's nearly at the limit of diminishing returns.
Répondre avec citation