> > > I also feel that the name of this library is a bit too vague. Some people > > > were asking first what means "headroom". It's actually for CPU headroom > > > monitoring. > > > What about "cpuheadroom", "cpuheadroomstat", "jobstat"? > > > > I think we can change the name to "cpuheadroom" as it describes more > clear this library. > > If you're focusing on CPU usage with possible actions, yes. > If you're focusing on decision helper, jobstat would be better IMHO.
We will change the name to "jobstats". Best regards Michal
