list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <>
To: "Vanak, Ibrahim" <>
Cc: Jeff Hostetler <>,
	"" <>
Subject: Re: GIT issue while cloning (fatal: pack is corrupted (SHA1 mismatch)) !!!
Date: Fri, 28 Jun 2019 19:55:33 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <TU4PR8401MB1216FC788B6A421F8FD82B2EE1FC0@TU4PR8401MB1216.NAMPRD84.PROD.OUTLOOK.COM>

On Fri, Jun 28, 2019 at 04:18:37PM +0000, Vanak, Ibrahim wrote:

> But HPUX Dev team have seen one significance difference, when they
> were triaging this issue, the ways GIT operations handled by 2 OSs: On
> linux, around 40 processes are spawned for handling a GIT operation
> whereas on HPUX only one process manages the operation. Is there
> something special being written for linux on GIT code ?

On Linux (and any platform that supports pthreads), Git will do the
lstat() operations to refresh the index in parallel. See the
core.preloadIndex option (which I think defaults to true).

If you have a very high-latency lstat() and your build does not have
pthread support, that could be a significant difference.

That might be worth exploring.


  reply	other threads:[~2019-06-28 23:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-28  9:10 Vanak, Ibrahim
2019-05-28  9:37 ` Jeff King
2019-05-28  9:51   ` Ævar Arnfjörð Bjarmason
2019-05-28 18:45   ` Vanak, Ibrahim
2019-05-28 21:30     ` Jeff King
2019-05-29  5:29       ` Vanak, Ibrahim
2019-05-29  9:06         ` Vanak, Ibrahim
2019-05-30 11:57           ` Jeff King
2019-06-11 16:39             ` Vanak, Ibrahim
2019-06-18 14:31               ` Vanak, Ibrahim
2019-06-18 17:15                 ` Jeff Hostetler
2019-06-28 16:18                   ` Vanak, Ibrahim
2019-06-28 23:55                     ` Jeff King [this message]
2019-05-28 10:16 ` Johannes Schindelin

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this inbox:

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).