Jitsi org join a meeting11/13/2023 ![]() If tomorrow every OS came with a built-in SIP client that actually worked and there was an actual successful deployment of consumer-grade SIP, demand for IPv6 would skyrocket and the ISP would get their act together or start losing customers over it. The ISP is still "evaluating" IPv6 because there's just no real end-user demand because besides ideology or specific requirements of a technical minority there just isn't any reason for the average user to need it. Even if you could get IPv6 right now (and you can with tunneling/VPN), what are you going to do with it? Big tech is quite happy with the loss of end-to-end connectivity since it enforces the need for a middleman, and they have no reason to make it easier for you to regain your independence. The problem is that there's no money to be made here, so no software is built to take advantage of end-to-end connectivity. It's actually no different to TURN (if you were behind a restrictive NAT), just that your TURN provider is now the tunnel broker and is independent of your communications service. Yes it's not really efficient but it will work especially if the only thing you use it for is communications. This is quite trivial to work around by just tunneling/VPN'ing to a IPv6 tunnel broker. That should at least bring the figure down to about 800 MB (jvb, jicofo, prosody, containerd, oauth2-proxy, nginx). If 2 GB idle memory usage is too much, then I would say ditch k3s entirely and handle everything with docker-compose, using Nginx as your reverse proxy. K3s-server makes up nearly half of the 2 GB idle figure, sitting at about 700 MB of usage (according to the top(1) command I ran for this post). But I was able to run a meeting with three people and share my screen with peak memory usage at 2.2 GB - again, for the whole system. The "actual" amount of memory that goes into running jvb and jicofo seems to be roughly 600 MB, which is still a lot to some, I guess. I simply ran "free -h" in my server and saw 2GB of memory usage. ![]() ), running the oauth2-proxy, then running the whole suite of Jitsi (sans Jibri, since I do not need the functionality it provides). ![]() I am counting the memory consumption of everything: running Linux (specifically Fedora Server 38), running k3s (which means CoreDNS, Klipper, Traefik. I should have clarified what I meant with the 2GB figure.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |