[pawelwentpawel]

Since last year I've been using Pixi.js (https://pixijs.com/) to create an app that puts video meetings into a 2d virtual space (https://flat.social). While learning how to build it, I got really (possibly a bit more than necessary) into optimising graphics performance to make sure it runs smoothly even for users who access it on potato laptops.

This includes pretty much every aspect of the rendering process - how often are elements updated, textures, masking, interpolation, fonts and making sure that nothing renders more often than it should. It's a challenging but pleasant process as the result of experimentation is usually easy to measure (FPS + memory usage).

PS. If you're into it as well - try Safari's web inspector for measuring performance and investigating which frames were dropped. I found it much easier to use for debugging than Chrome.

[kapitanjakc]

I was reading this and although I know nothing about the topic, these thoughts just entered my mind.

While on meeting many people are in mute. In that case something of the sort can be done that position/part of people on mute is rendered less frequently.

And people who don't have their camera on are only rendered once