Review the conditions to show the "High FFMPEG CPU usage" message.

[Mincka]

I get the "High FFMPEG CPU usage" showing for a 4K camera with a load of 22%.
Since I have other cameras with lower resolutions, it's "above the average" but not high for my setup.

frigate/web/src/hooks/use-stats.ts

Lines 73 to 79 in 3f1ab66

	if (!isNaN(ffmpegAvg) && ffmpegAvg >= CameraFfmpegThreshold.error) {
	problems.push({
	text: `${capitalizeFirstLetter(name.replaceAll("_", " "))} has high FFMPEG CPU usage (${ffmpegAvg}%)`,
	color: "text-danger",
	relevantLink: "/system#cameras",
	});
	}

Would it be possible to change the logic for showing this message?

[NickM-27]

We can maybe rethink the ranges for ffmpeg, the problem is though we want to make sure users who don't run hwaccel are made aware of the problem

[Mincka]

Certainly, and in that case, "High" would be something way over 20% I guess.

frigate/web/src/types/graph.ts

Lines 46 to 49 in eda52a3

	export const CameraFfmpegThreshold = {
	warning: 20,
	error: 20,
	} as Threshold;

An alternative could be the ability to override these values in the configuration file.

[NickM-27]

not necessarily, ffmpeg usage can be ~ 20% on my server for example but with hwaccel it is 2%. Will have to see what makes sense

[Mincka]

So the value can be anything, you won't be able to tell if it's good or bad.
Also, you cannot predict what will be the load difference with / without hardware acceleration.

Aren't you able to tell if hardware acceleration is used or not?

It could be an additional condition to avoid displaying this message or adjust the threshold value in that case.

[NickM-27]

in general, 20% is quite high for ffmpeg with hwaccel and usually indicates an issue or something that can be optimized. This message is there to alert people and encourage them to seek support or fix the issue. Not sure if we will want to change this, but in any case like I said will think about what might make sense