[Piuparts-devel] _throttle_if_overloaded stability

Andreas Beckmann anbe at debian.org
Mon Feb 25 02:56:04 UTC 2013

On 2013-02-25 02:45, Dave Steele wrote:
> This has the potential to oscillate in the presence of multiple

possible, but I see no solution without having the slaves communicate
with each other (or have a single but multithreaded slave)
and maybe I have seen such cases
but usually for a longer high-load period one slave seems to go on a
longer pause

> slaves. I'd recommend reducing the secs range to under the loadavg
> time constant (say to 30-60 seconds, 15 to 45 would be better), and
> skipping the delay accumulation.

wouldn't that make the situation worse? as many more slaves will hit the
short time slot where load is low enough for resume

> If you are in a situation where 30 seconds isn't long enough, making
> it longer is not going to help.

I'm more concerned about these longer periods, e.g. while compiling gcc
with -j8. Or while piuparts-report was running and eating 5 GB ... and
texlive-full was tested. In several slaves in parallel. That might lead
to thrashing and swapping (since my tmpdir is on tmpfs - that works
really well except for a handful of packages that require installation
of gigabytes of unpacked packages

and I don't really want to see too much "overloaded, sleeping" noise in
the terminal

> It could also help to add a bit of noise to the load_resume threshold.

good idea, I'll try it, and for max-load, too


More information about the Piuparts-devel mailing list