|
Re: OpenSER dimensioning. How many calls/sec can it set up?: msg#00486voip.openser.user
unplug writes: > mediaproxy spends much of the CPU to handle the call compared with > rtpproxy. From the result that I made in the load test, the number of > concurrent call is much much less than we expected. > maximum concurrent call using mediaproxy (openser & mediaproxy in the > same server): 30 > maximum concurrent call using rtpproxy (openser & rtpproxy in the same > server): 60 you can distribute mediaproxy to as many host you want. or are you saying that mediaproxy module functions use_mediaproxy/end_mediaproxy are the bottleneck? -- juha |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: libradiusclient-ng-so.2 cann't share: 00486, raviprakash sunkara |
|---|---|
| Next by Date: | AW: split signaling from rtp: 00486, Franz Edler |
| Previous by Thread: | Re: OpenSER dimensioning. How many calls/sec can it set up?i: 00486, unplug |
| Next by Thread: | Re: OpenSER dimensioning. How many calls/sec can it set up?: 00486, unplug |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |