public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Jim Meyering <jim@meyering.net>
Cc: overseers@gcc.gnu.org
Subject: Re: Multiple cvs/git mirror tasks?
Date: Tue, 24 Jul 2012 18:20:00 -0000	[thread overview]
Message-ID: <500EE750.705@redhat.com> (raw)
In-Reply-To: <87pq7q8kwp.fsf@rho.meyering.net>

On 07/20/2012 12:19 PM, Jim Meyering wrote:
> At first glance, you may think there are three invocations of the script,
> but as recently discussed here, that's merely due to a subshelled
> pipeline in the script: each element of the pipeline ends up looking
> (in ps output) like another invocation of the parent script.  It really
> was invoked only once.

Right, but in the ps output I sent before, there were two gdb runs (each 
with 3 processes) running at the same time.

> I'm leery about adding naive cross-project locks, because that could
> let a busy project starve one that needs only a tiny update.
>
> Using lockfile(1) and a timeout might help.
>
> I could add a per-project locking mechanism to prevent e.g., two gdb
> syncs from running in parallel when the first one takes more than the
> 30m between cron invocations.  That could save some system resources,
> but would not improve correctness or integrity.

That makes sense to me.  The times when it would run long are likely to 
correspond with times when system resources are tightest, as with the 
time I noticed.

Jason

  reply	other threads:[~2012-07-24 18:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 15:21 Jason Merrill
2012-07-13 15:43 ` Jim Meyering
2012-07-13 15:55   ` Frank Ch. Eigler
2012-07-13 16:05     ` Jim Meyering
2012-07-13 16:12       ` Jim Meyering
2012-07-13 16:17         ` Jim Meyering
2012-07-16 18:52   ` Jason Merrill
2012-07-20 16:20     ` Jim Meyering
2012-07-24 18:20       ` Jason Merrill [this message]
2012-07-25  8:08         ` Jim Meyering
2012-07-25 13:05           ` Jason Merrill

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=500EE750.705@redhat.com \
    --to=jason@redhat.com \
    --cc=jim@meyering.net \
    --cc=overseers@gcc.gnu.org \
    /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).