Increase duration before DPB marks a port frozen

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Increase duration before DPB marks a port frozen

Kurt Mosiejczuk-9
With the default of 10 seconds with no response, my DPB status screen
stays almost entirely red for the duration of the sparc64 bulk.

Increasing it to 45 seconds tends to eliminate the red except for things
that are actually stuck... and rust ports. :)

How would folks feel about increasing to 45 seconds?

Index: Clock.pm
===================================================================
RCS file: /cvs/ports/infrastructure/lib/DPB/Clock.pm,v
retrieving revision 1.16
diff -u -p -r1.16 Clock.pm
--- Clock.pm 24 Oct 2019 15:05:22 -0000 1.16
+++ Clock.pm 13 Feb 2020 22:19:45 -0000
@@ -163,7 +163,7 @@ sub frozen_message
  $unchanged .= int($diff/3600)." HOURS!";
  } elsif ($diff > 300) {
  $unchanged .= int($diff/60)."mn";
- } elsif ($diff > 10) {
+ } elsif ($diff > 45) {
  $unchanged .= int($diff)."s";
  } else {
  $unchanged = "";

Reply | Threaded
Open this post in threaded view
|

Re: Increase duration before DPB marks a port frozen

Stuart Henderson
On 2020/02/13 17:22, Kurt Mosiejczuk wrote:
> With the default of 10 seconds with no response, my DPB status screen
> stays almost entirely red for the duration of the sparc64 bulk.
>
> Increasing it to 45 seconds tends to eliminate the red except for things
> that are actually stuck... and rust ports. :)
>
> How would folks feel about increasing to 45 seconds?

I would be happy with that, I see a lot of 'frozen for XX' on i386 too
and 45s feels like a good cutoff to me.

> Index: Clock.pm
> ===================================================================
> RCS file: /cvs/ports/infrastructure/lib/DPB/Clock.pm,v
> retrieving revision 1.16
> diff -u -p -r1.16 Clock.pm
> --- Clock.pm 24 Oct 2019 15:05:22 -0000 1.16
> +++ Clock.pm 13 Feb 2020 22:19:45 -0000
> @@ -163,7 +163,7 @@ sub frozen_message
>   $unchanged .= int($diff/3600)." HOURS!";
>   } elsif ($diff > 300) {
>   $unchanged .= int($diff/60)."mn";
> - } elsif ($diff > 10) {
> + } elsif ($diff > 45) {
>   $unchanged .= int($diff)."s";
>   } else {
>   $unchanged = "";
>

Reply | Threaded
Open this post in threaded view
|

Re: Increase duration before DPB marks a port frozen

Marc Espie-2
On Thu, Feb 13, 2020 at 10:35:18PM +0000, Stuart Henderson wrote:

> On 2020/02/13 17:22, Kurt Mosiejczuk wrote:
> > With the default of 10 seconds with no response, my DPB status screen
> > stays almost entirely red for the duration of the sparc64 bulk.
> >
> > Increasing it to 45 seconds tends to eliminate the red except for things
> > that are actually stuck... and rust ports. :)
> >
> > How would folks feel about increasing to 45 seconds?
>
> I would be happy with that, I see a lot of 'frozen for XX' on i386 too
> and 45s feels like a good cutoff to me.
>
> > Index: Clock.pm
> > ===================================================================
> > RCS file: /cvs/ports/infrastructure/lib/DPB/Clock.pm,v
> > retrieving revision 1.16
> > diff -u -p -r1.16 Clock.pm
> > --- Clock.pm 24 Oct 2019 15:05:22 -0000 1.16
> > +++ Clock.pm 13 Feb 2020 22:19:45 -0000
> > @@ -163,7 +163,7 @@ sub frozen_message
> >   $unchanged .= int($diff/3600)." HOURS!";
> >   } elsif ($diff > 300) {
> >   $unchanged .= int($diff/60)."mn";
> > - } elsif ($diff > 10) {
> > + } elsif ($diff > 45) {
> >   $unchanged .= int($diff)."s";
> >   } else {
> >   $unchanged = "";
> >
>
Okay.