what is jitter's measurement unit in `producer.getStats()`?

hi .
in our application we are showing user details about their network like packet-loss and …
one of most important metrics is jitter or inbound-jitter and outbound-jitter
we are using server-side calculation of producer.getStats() to calc outbound-jitter and because we don’t have consumers jitter we do inbound-jitter calculation locally just using client side getStats().
anyway …
please look at this result :
as you can see producer jitter is about 10x of consumer jitter . i tested with many different networks and devices on my service and same result .

1- my question is this in new updates we changed anything about jitter measurement unit or calculation ? (i know i already read release note)

2- what is current jitter measurement unit ? milliseconds ?

thank you.


thank you .
so there is a problem properly .
i was updated mediasoup from 3.12.6 to 3.13.15. after that our clients reported the jitter number is high .
do you have any recommendation how can i debug it and find this congestion ?

Well that depends, I can’t speak on versions of mediasoup, I’ve not seen an update have such drastic impact on network and many would report it. However for sake of trialing down-grade and switch back to see if it’s consistent for fastest debugging.

If you can’t find consistency between the versions you would likely be having some network issues and this could be temporary from several hours to days and affect specific users sometimes.

A trace-route helps one understand where latency is occurring and if major host is affected at specific hops. With testing many end-points with server you can determine if server is fine.

Sometimes the user has poor connection and there’s little we can do but perhaps offer more servers in different locations or they utilize a VPN/etc to get the best hops.

1 Like

There’s a reason why I run more than one media server, we could be online for months then a DDOS or network outages occur and I have everyone complaining. Designing a system to allow users to switch servers is most optimal.

1 Like

thanks for your response .
i down-graded version to previous version and seems like problem is solved . i think maybe calculation algorithm maybe changed and measurement unit has been changed (from Seconds to Milliseconds)
how can i check changes ? i mean which files i should check in worker source code ?

and something else i figured out is the jitter in lower version is less than higher version . i do not know really whats happening between these 2 versions but was maybe congestion controller did changed ?

version : 3.12.16

version : 3.13.15

same network / same host

i also checked the latest version (via live demo) and got same result.