From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; spf=pass (mailfrom) smtp.mailfrom=irif.fr (client-ip=2001:660:3301:8000::1:2; helo=korolev.univ-paris7.fr; envelope-from=jch@irif.fr; receiver=) Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) by mail.toke.dk (Postfix) with ESMTPS id 93A127CA3B8 for ; Tue, 12 Jan 2021 22:02:35 +0100 (CET) Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 10CL2ZOQ030506; Tue, 12 Jan 2021 22:02:35 +0100 Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 37065241F3; Tue, 12 Jan 2021 22:02:35 +0100 (CET) X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id Sx9q8XX1l2H3; Tue, 12 Jan 2021 22:02:33 +0100 (CET) Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 7D406241F1; Tue, 12 Jan 2021 22:02:33 +0100 (CET) Date: Tue, 12 Jan 2021 22:02:33 +0100 Message-ID: <87k0shq36e.wl-jch@irif.fr> From: Juliusz Chroboczek To: Dave Taht In-Reply-To: References: <87k0siqndj.wl-jch@irif.fr> <87pn2aup3o.fsf@toke.dk> <878s8yqcmh.wl-jch@irif.fr> <871reqqb52.wl-jch@irif.fr> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.1 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-8859-1 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Tue, 12 Jan 2021 22:02:35 +0100 (CET) X-Miltered: at korolev with ID 5FFE0E6B.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 5FFE0E6B.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/ X-j-chkmail-Score: MSGID : 5FFE0E6B.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000 X-j-chkmail-Status: Ham Content-Transfer-Encoding: quoted-printable Message-ID-Hash: GXVF6L7FDDD7N7BIZTRGJYV5GCDNAGDD X-Message-ID-Hash: GXVF6L7FDDD7N7BIZTRGJYV5GCDNAGDD X-MailFrom: jch@irif.fr X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header CC: galene@lists.galene.org X-Mailman-Version: 3.3.2 Precedence: list Subject: [Galene] Re: fq-codel trashing List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Post: List-Subscribe: List-Unsubscribe: > please try cake. Both my servers are used in production right now, so I'm not very keen on experimenting. I should have some funding for Gal=E8ne soon. > And collect a capture on the underlying hw if possible. I don't have access to the underlying hardware, it's a cloud provider. >> * I need to think of a better way of prioritising voice over video whe= n >> under load; > I take it (I really didn't understand) that unbundling these two types > is not currently feasible in the javascript or webbrowser. [...] > collisions in fq_codel start to occur as the sqrt(1024) so at 70 users > the odds are 2-3 of your sessions were colliding. I don't think the network is the problem. The problem is that there's a lot of buffering in Pion, and as I push packets down the layers, I have no way of finding out the amount already queued -- so when we're short on CPU, the video tends to crowd out the audio. I'm not sure what the solution is. >> Gal=E8ne recovered after some people switched their cameras off, I did= n't >> need to restart anything. At the highest point, Gal=E8ne was at 270% = CPU, >> and the TURN server was using another 50%. That's on a four-core VM. > but it does sound like more virtual cores will help at this load? According to profiling, 60% CPU time is spent in the write system call. > you are context switching like crazy most likely also. I'll measure next time, but I doubt it: Go's scheduler operates almost entirely in userspace. -- Juliusz