1. Yes, it has pretty high CPU usage unfortunately and that’s despite the attempts of Jitsi to offload h264 encoding onto the clients. You could in theory lock it to standard definition video though which would reduce CPU usage a lot.

2. We did not on this instance but we did using their Docker instance which was very straightforward to setup: https://github.com/jitsi/docker-jitsi-meet#jitsi-broadcastin...

I don’t believe it needs a VM per conference - maybe a ffmpeg process per instance?

Here's the Jitsi architecture which best I can tell shows JIBRI (recording part) as a separate, single container: https://i.imgur.com/oDSRzF4.png