Message ID | 20250411-bb-pressure-improvements-v1-1-7d9e3593167f@bootlin.com |
---|---|
State | New |
Headers | show |
Series | Improvements around BB_PRESSURE_* variables | expand |
On Fri, Apr 11, 2025 at 4:46 PM Antonin Godard via lists.yoctoproject.org <antonin.godard=bootlin.com@lists.yoctoproject.org> wrote: > > By default all the pressure changes are printed on the console and > generate a lot of spam to users using the BB_PRESSURE_* variables. > Decrease the default verbosity to bb.debug (level 1, so can be seen with > -D). Isn't "a lot of these messages" a proof that the BB_PRESSURE_* variables aren't set correctly? I find them quite useful and using -D by default in my builds would bring even "more spam". But in worse case I'll just revert this for my builds. Cheers, > Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> > --- > lib/bb/runqueue.py | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/lib/bb/runqueue.py b/lib/bb/runqueue.py > index 8fadc8338..adfe3c7a1 100644 > --- a/lib/bb/runqueue.py > +++ b/lib/bb/runqueue.py > @@ -219,7 +219,7 @@ class RunQueueScheduler(object): > pressure_state = (exceeds_cpu_pressure, exceeds_io_pressure, exceeds_memory_pressure) > pressure_values = (round(cpu_pressure,1), self.rq.max_cpu_pressure, round(io_pressure,1), self.rq.max_io_pressure, round(memory_pressure,1), self.rq.max_memory_pressure) > if hasattr(self, "pressure_state") and pressure_state != self.pressure_state: > - bb.note("Pressure status changed to CPU: %s, IO: %s, Mem: %s (CPU: %s/%s, IO: %s/%s, Mem: %s/%s) - using %s/%s bitbake threads" % (pressure_state + pressure_values + (len(self.rq.runq_running.difference(self.rq.runq_complete)), self.rq.number_tasks))) > + bb.debug(1, "Pressure status changed to CPU: %s, IO: %s, Mem: %s (CPU: %s/%s, IO: %s/%s, Mem: %s/%s) - using %s/%s bitbake threads" % (pressure_state + pressure_values + (len(self.rq.runq_running.difference(self.rq.runq_complete)), self.rq.number_tasks))) > self.pressure_state = pressure_state > return (exceeds_cpu_pressure or exceeds_io_pressure or exceeds_memory_pressure) > elif self.rq.max_loadfactor: > > -- > 2.47.0 > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > View/Reply Online (#6736): https://lists.yoctoproject.org/g/docs/message/6736 > Mute This Topic: https://lists.yoctoproject.org/mt/112211584/3617156 > Group Owner: docs+owner@lists.yoctoproject.org > Unsubscribe: https://lists.yoctoproject.org/g/docs/unsub [martin.jansa@gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- >
diff --git a/lib/bb/runqueue.py b/lib/bb/runqueue.py index 8fadc8338..adfe3c7a1 100644 --- a/lib/bb/runqueue.py +++ b/lib/bb/runqueue.py @@ -219,7 +219,7 @@ class RunQueueScheduler(object): pressure_state = (exceeds_cpu_pressure, exceeds_io_pressure, exceeds_memory_pressure) pressure_values = (round(cpu_pressure,1), self.rq.max_cpu_pressure, round(io_pressure,1), self.rq.max_io_pressure, round(memory_pressure,1), self.rq.max_memory_pressure) if hasattr(self, "pressure_state") and pressure_state != self.pressure_state: - bb.note("Pressure status changed to CPU: %s, IO: %s, Mem: %s (CPU: %s/%s, IO: %s/%s, Mem: %s/%s) - using %s/%s bitbake threads" % (pressure_state + pressure_values + (len(self.rq.runq_running.difference(self.rq.runq_complete)), self.rq.number_tasks))) + bb.debug(1, "Pressure status changed to CPU: %s, IO: %s, Mem: %s (CPU: %s/%s, IO: %s/%s, Mem: %s/%s) - using %s/%s bitbake threads" % (pressure_state + pressure_values + (len(self.rq.runq_running.difference(self.rq.runq_complete)), self.rq.number_tasks))) self.pressure_state = pressure_state return (exceeds_cpu_pressure or exceeds_io_pressure or exceeds_memory_pressure) elif self.rq.max_loadfactor:
By default all the pressure changes are printed on the console and generate a lot of spam to users using the BB_PRESSURE_* variables. Decrease the default verbosity to bb.debug (level 1, so can be seen with -D). Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> --- lib/bb/runqueue.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)