From: Andrew Cagney <ac131313@redhat.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Phil Edwards <phil@jaj.com>, overseers@sources.redhat.com
Subject: Re: NTP, and gccadmin's crontab about to be activated
Date: Wed, 22 Jan 2003 15:19:00 -0000 [thread overview]
Message-ID: <3E2EB68E.2090009@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0301210058430.5687-100000@kern.srcf.societies.cam.ac.uk>
> On Mon, 20 Jan 2003, Andrew Cagney wrote:
>
>
>> > And update_web_docs, but that should be much faster on the new machine,
>> > and be finished long before GDB's crontab starts.
>
>>
>> The current schedule was carefully arranged and for good a reason. It
>> balanced the system load. GCC's task (the longest running and heavest)
>> at the time when the system had the lightest load (the middle of the
>> apec day when europe and america were in bed).
>
>
> The timing of update_web_docs, if carefully arranged, was arranged when
> update_web_docs was a rather smaller job (only generating HTMl manuals,
> not running TeX). But the current update_web_docs still consistently ran
> in under 3 minutes on the old system, and is of course quicker on the new
> one.
Ah! Ok, ignore me then :-)
> The only one of GCC's jobs that takes a significant amount of time is the
> weekly snapshot run, at 16:40 on Mondays. That's the only one for which
> scheduling the time not to clash with other jobs is important.
Andrew
next prev parent reply other threads:[~2003-01-22 15:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 6:26 Phil Edwards
2003-01-20 14:40 ` Christopher Faylor
2003-01-20 19:01 ` Andrew Cagney
2003-01-20 19:04 ` Phil Edwards
2003-01-20 19:07 ` Joseph S. Myers
2003-01-20 19:49 ` Andrew Cagney
2003-01-21 1:03 ` Joseph S. Myers
2003-01-22 15:19 ` Andrew Cagney [this message]
2003-01-20 19:19 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E2EB68E.2090009@redhat.com \
--to=ac131313@redhat.com \
--cc=jsm28@cam.ac.uk \
--cc=overseers@sources.redhat.com \
--cc=phil@jaj.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).