I've experienced low video frame rates (20 when 25 is expected) when using Chrome fake video with our WebRTC app. The issue only occurs with .mjpeg files, and does not with .y4m.
I think I've experienced higher CPU usage on our test containers in Docker, but can't be sure without more accurate logging.
According to our video expert, .mjpeg requires some extra decoding by Chrome to use, which could explain the (potentially) higher CPU usage. The browser uses libyuv library for decoding a single video frames, but from his experience, this library is well optimised and shouldn't have any issues.
Has anyone else experienced performance issues with mjpeg, or who can explain the issue?