Should `BG_CPUIO` type be slightly more aggressive?

[asyync1024]

Hi!

So I recently found out that the BG_CPUIO type has rules that are very passive, which affects programs like rsync when doing some heavy task like compiling.

For instance, let's say I am compiling and then I take a backup of my system with rsync, the backup is probably not going to complete before the compilation stops, this is a problem as rsync is a pretty important program for various tasks.

The name of the type implies that the process only needs CPUIO most, but having "ioclass": "idle" seems conterproductive. Since rsync doesn't see to fit in any other category, I think the parameters should be reconsidered?

Thanks!

[Aarrayy]

Or we could add another type.

[asyync1024]

Or we could add another type.

Yeah, but I don't really have an idea of what type to create for rsync, I think setting "ioclass": "best-effort" would fix this issue?

As the main purpose of BG_CPUIO type is supposed to be "Mostly Background IO", but it's not going to be able to utilize the IO at all at intensive times like compiling.

Though I think your approach is better.

[Aarrayy]

Done: https://github.com/CachyOS/ananicy-rules/blob/master/00-types.types#L24