You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello team,
I don't know how to explain my issue but please take a look in https://bugs.chromium.org/p/webrtc/issues/detail?id=14012#c1 where I post what is really wrong and the answer from the owners.
In two words- when I use oldest version of webrtc wich use older version of usrsctp CPU is just ok, but newest ver of webrtc using newest usrsctp there is a spikes and high demand of CPU load into newtork threads.
I am asking you to see and resolve this issue if possible.
The text was updated successfully, but these errors were encountered:
Sorry but you're filing this in the wrong project. Newest Chromium does not use usrsctp anymore and that's most likely the exact reason for the big performance difference. You'll need to talk to Google folks.
Hello team,
I don't know how to explain my issue but please take a look in https://bugs.chromium.org/p/webrtc/issues/detail?id=14012#c1 where I post what is really wrong and the answer from the owners.
In two words- when I use oldest version of webrtc wich use older version of usrsctp CPU is just ok, but newest ver of webrtc using newest usrsctp there is a spikes and high demand of CPU load into newtork threads.
I am asking you to see and resolve this issue if possible.
The text was updated successfully, but these errors were encountered: