From: Jason Molenda <jason@molenda.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: overseers@sourceware.cygnus.com
Subject: htdig crontab on sourceware
Date: Tue, 17 Apr 2001 11:52:00 -0000 [thread overview]
Message-ID: <20010417115150.A5011@shell17.ba.best.com> (raw)
In-Reply-To: <Pine.BSF.4.30.0104072306280.77238-100000@dair.pair.com>
Hi Hans-Peter,
37 2 * * * /bin/sh /sourceware/htdig/gcc/bin/htupdate.sh
37 7 * * * /bin/sh /sourceware/libre/infra/bin/htupdate-sourceware.sh
The sourceware htdig run is causing some load problems. The actual
htdig process didn't get started until 10:30am, and the system is
hella busy at that point. sourceware is currently running a load
average of over ten; this just isn't a good time to be running
htdig. (there isn't any one culprit - there are a lot of people
doing anoncvs updates, web accesses, sending e-mail, etc, nad htdig
is just one more busy process on top of all that.)
How about we movie it to 20.00 localtime? By 8pm at night the
system load is very low and a little indexing won't cause significant
problems. We could push the gcc htupdate back to 3.30 localtime
if you think they might run concurrently and eat up all the disk
space.
Jason
next prev parent reply other threads:[~2001-04-17 11:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 19:40 hard disk recovered? Christopher Faylor
2001-04-07 18:49 ` Christopher Faylor
2001-04-12 11:48 ` law
2001-12-31 19:40 ` Hans-Peter Nilsson
2001-04-07 19:23 ` Hans-Peter Nilsson
2001-12-31 19:40 ` Christopher Faylor
2001-04-07 19:30 ` Christopher Faylor
2001-12-31 19:40 ` Hans-Peter Nilsson
2001-04-07 19:55 ` Hans-Peter Nilsson
2001-12-31 19:40 ` Christopher Faylor
2001-04-07 20:04 ` Christopher Faylor
2001-12-31 19:40 ` Hans-Peter Nilsson
2001-04-07 20:14 ` Hans-Peter Nilsson
2001-04-17 11:52 ` Jason Molenda [this message]
2001-04-17 13:28 ` htdig crontab on sourceware Hans-Peter Nilsson
2001-04-17 14:28 ` Christopher Faylor
[not found] ` <20010417133358.A4238@shell17.ba.best.com>
2001-04-18 8:20 ` Jason Molenda
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=20010417115150.A5011@shell17.ba.best.com \
--to=jason@molenda.com \
--cc=hp@bitrange.com \
--cc=overseers@sourceware.cygnus.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).