increasing the number of libwebsocket service threads of mod_audio_fork module

[spointer]

Hello Dave,
When i run sipp for performance test(for example, peak call to 50 and call rate to 3 cps), it seems the remote audio stream is delayed and even not received at all.
I changed MOD_AUDIO_FORK_SERVICE_THREADS to 5 but had no luck and even i followed up this link and changed freeswitch configuration but had no luck either.

https://stackoverflow.com/questions/53609817/freeswitch-blocked

Is there a reason for limiting the max thread number to 5?
Could you provide the way to increase the number over 5?

Any suggestions are appreciated.

[davehorton]

what size of instance are you running on? I have not seen this issue before in my testing/deployments

[spointer]

My instance size is 4 vcpu and 8G memory.

[davehorton]

you should be getting much better performance than that. How you are you measuring audio delay? Are you certain the delay is not on the websocket server (receiving) side?

[davehorton]

also I would not make that change you cited in the freeswitch link

[spointer]

ok, i will take a closer look at my code now and let you know

[davehorton]

mod_audio_fork uses libwebsockets, and lws only sends data when the socket is in a writable state. If the downstream server falls behind, this will cause the module to buffer audio until the socket becomes writable

[spointer]

ok, i found there is no audio stream delay in freeswitch module with another testing, sorry for bothering you.