> On the automation part, it would be pretty easy to do regularly(daily?) stats > of jobs for that period of time and dump them into an sql database. > Then a select statement where cpu_efficiency is less than desired value and > get the list of not so nice users on which you can apply whatever > warnings/limits you want to do.
Assuming the existence of collection and collation of the penalty data (e.g. in an SQL database) you could consider using a site factor plugin to deprioritize scheduling priority w/o the need to alter an association in the accounting database. https://slurm.schedmd.com/site_factor.html