git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Raible <raible@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Eric Raible <raible+git@gmail.com>, git@vger.kernel.org
Subject: Re: RFH: spawning pager takes long time when when unconnected from  network
Date: Tue, 10 Feb 2009 03:39:11 -0800	[thread overview]
Message-ID: <279b37b20902100339w6e4d215cua41887c65f7c37bc@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0902101159300.10279@pacific.mpi-cbg.de>

On Tue, Feb 10, 2009 at 3:03 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> You could also try to set it to /bin/false, just so you know if the delay
> is caused by the shell startup.
>
> In my experience, such intermittent delays are often triggered by some
> (mostly unnecessary) calls to either DNS (which might hang for quite some
> time) or domain controllers (same).  These can be triggered by shell
> startup looking for the user or host name.
>
> However, I am just fishing here, as I cannot begin to get an idea what is
> happening on your side.
>
> Also, it does not help that the platform is Windows, an OS I am mostly
> unfamiliar with.  But there have to be profiling tools for that platform
> where you should be able to see what function is blocking (I assume it is
> a blocking call, of course).
>
> Ciao,
> Dscho

Toggling core.pager btwn /bin/false and less is slow the first time,
then quick subsequent times.  Setting core.pager to "echo no pager"
gives the same behavior.

What would be handy is a windows version of strace, but the one
that I found doesn't seem functional.  gdb is useless for this
(so far, anyway).    I think it's time to sleep on this.

Thanks - Eric

  reply	other threads:[~2009-02-10 11:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  2:07 RFH: spawning pager takes long time when when unconnected from network Eric Raible
2009-02-10  2:27 ` Eric Raible
2009-02-10  7:57 ` Johannes Sixt
2009-02-10  9:20   ` Eric Raible
2009-02-10 10:24     ` Johannes Schindelin
2009-02-10 10:53       ` Eric Raible
2009-02-10 11:03         ` Johannes Schindelin
2009-02-10 11:39           ` Eric Raible [this message]
2009-02-10 11:07         ` Jeff King
2009-02-10 11:55           ` Eric Raible
2009-02-10 16:34             ` Jay Soffian
2009-02-10 11:09         ` Andreas Ericsson

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=279b37b20902100339w6e4d215cua41887c65f7c37bc@mail.gmail.com \
    --to=raible@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=raible+git@gmail.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 NNTP newsgroup(s).