[OpenSIPS-Users] Mediaproxy speed calculations
daniel.zanutti at gmail.com
Tue Mar 28 13:55:00 EDT 2017
Thanks for answering.
The machine is not overloaded, actually i have the same problem with 10
calls or 1000 calls. I can confirm there is a lot of traffic on it, for
1 220.127.116.11 2.6.1 108h09'30" 6.71Mbps 413 audio 413 Active
2 18.104.22.168 2.6.5 95h50'12" 0bps 435 audio 435 Active
3 22.214.171.124 2.6.5 95h50'16" 0bps 382 audio 382 Active
4 126.96.36.199 2.6.5 108h08'38" 7.29Mbps 402 audio 402 Active
5 188.8.131.52 2.6.5 107h59'38" 6.41Mbps 375 audio 375 Active
eth0 304104 304104 0 0 20903.40 kbits/sec
Mar 28 14:51:45 MP-104 media-relay: warning: Aggregate speed
calculation time exceeded 10ms: 15214 us for 418 sessions
load average: 0.56, 0.61, 0.63
Linux MP-104 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07)
You are right about being virtual, but I'm sure the server is not
overloaded because I have the same problem during the night, with almost no
traffic. During the day, it MAY be overloaded but surely not during the
night and this information never shows up on these relays.
Is there any way to force it? Could you give some directions?
On Tue, Mar 28, 2017 at 2:27 PM, Dan Pascu <dan at ag-projects.com> wrote:
> On 24 Mar 2017, at 19:51, Daniel Zanutti wrote:
> > Hi
> > Looks like i'm diving deep on mediaproxy.
> > Some of our relays are not calculating the speed on the network. If I
> restart a couple times it starts calculating fine.
> > I found this log:
> > media-relay: warning: Aggregate speed calculation time exceeded
> 10ms: 11644 us for 222 sessions
> > Is there any solution to always calculate?
> The relay always calculates. That is just a warning when it takes too
> long, but the calculation still took place.
> The reasons why you might not see traffic:
> 1. There is no actual traffic, despite having sessions setup, the devices
> do not send media
> 2. There is traffic but for some reason reading the traffic information
> from the kernel fails (I have no idea why that could happen, except maybe a
> severely overloaded virtual machine - see below)
> I noticed something very wrong with that warning. On a machine running on
> a Core I7 from 2012 (Sandy Bridge architecture, so not the latest hardware,
> but something from 5 years ago), the calculation for 222 sessions, takes 20
> us (that is micro seconds). You got 11644 us, which is approximately 600
> times slower. Which means your virtual machine is severely overloaded, or
> the amount of resources it has allocated from the real hardware is abysmal.
> On the same machine I mentioned before, having 2000 active sessions
> results in the speed calculations taking 170 us, which is well below the
> warning limit of 10 ms. Which means, the relay can drive thousands of
> sessions and you'll never see the warning.
> In conclusion, unless you run on a severely overloaded system, or a very
> underpowered virtual machine, you should never see that warning and seeing
> the warning doesn't mean that calculations didn't take place.
> Users mailing list
> Users at lists.opensips.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users