Thank you for your suggestions; I have noticed a very strange symptom but I've yet to determine if it actually affects call handling or not. When the -relay is heavily loaded it'll have the load spread out across the cores and then, suddenly, the CPU usage appears to drift over to a single core and max it out for a bit, with the other cores doing nothing.... and then it all spreads out again. The heavier loaded it is, the more time it spends on one core. Very strange. I installed irqbalance but it appears not to make a difference.
I'm hoping the worst this may cause is a slight delay in a call starting up with an allocated pair of media ports in iptables forwarding, rather than call audio distortion. Have you ever seen anything like this? - JP On Thu, Apr 5, 2012 at 6:58 AM, Saúl Ibarra Corretgé <[email protected]> wrote: > Hi, > >> >> Saúl, >> >> You called it. Complete turn around in load-out - no more port >> complaints and at 900 calls I'm seeing around 20% usage across four >> cores. And the 'apt-get update' updates -relay for me, which I was >> expecting to have to build (like I did initially), so I'm very >> pleased. >> > > I'm happy it works for you now :-) > >> When the system is humming along at 900 calls I started noticing these pop >> up: >> warning: Aggregate speed calculation time exceeded 10ms: 10401us for >> 431 sessions >> Googling shows that this is related to some statistics, so I've turned >> it off for now to see how far I can push media-proxy. >> > > It's just an indicator of how much data MediaProxy is relaying, of course as > number of sessions goes up, this calculation takes time, and while this > calculation is in progress the relay can't accept new sessions. You can > either sample at longer intervals, thus having a less accurate measurement, > or just disable it, in case you don't care about it. > >> Would you be able to recommend some other settings that I should make >> to help mediaproxy-relay push as many calls as possible? >> > > Given the fact that the relayed traffic is UDP I'm not sure if something can > be tweaked in the kernel, but one thing you can check is interrupts. See if > they are hitting a single CPU (check /proc/interrupts) and if so install > irqbalance so that interrupts are balanced among the cores. Good network > cards also help, of course :-) > > Given the fact that MediaProxy doesn't do much while the kernel is relaying > the traffic, you'll probably hit limits related to networking first. > Nevertheless, MediaProxy was designed with horizontal scalability in mind, so > if you need to handle more calls, you can add more relays :-) Also don't > forget that a relay can be connected to several dispatchers. > > > Regards, > > -- > Saúl Ibarra Corretgé > AG Projects > > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
