mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Derrick Stolee <>
To: Jeff Hostetler <>, Jeff King <>
Cc: Git Mailing List <>,
	Junio C Hamano <>,
	Ben Peart <>,
	Jameson Miller <>
Subject: Re: Question about the ahead-behind computation and status
Date: Fri, 15 Dec 2017 10:43:34 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 12/15/2017 10:08 AM, Jeff Hostetler wrote:
> On 12/15/2017 5:08 AM, Jeff King wrote:
>> On Thu, Dec 14, 2017 at 04:49:31PM -0500, Jeff Hostetler wrote:
>>> [*] Sadly, the local repo was only about 20 days out of
>>>      date (including the Thanksgiving holidays)....
>> Taking 20 seconds to traverse 20 days worth of history sounds pretty
>> awful. How many commits is it?
> 150,000 commits, give or take.  The graph is many thousands of lanes
> wide because of the merges and that isn't helping.
> (But I should give you folks lots of credit -- it *only* took 20
> seconds to find, unzip and decode 150,000 commit objects and walk
> the commit graph.)

To give a few more data points, I created similar situation by checking 
out a big repo I hadn't updated in three months and it was 16,000 
commits behind. That took 1.5s to calculate the ahead/behind. Moving it 
100,000 commits behind it took 5s. This repo has about 300,000 total 
commits versus the 1.5 million commits in the Windows repo.

The biggest reason for the 20 seconds is not just the number of commits 
in the ahead/behind but how many commits are walked (including common to 
both branches) before paint_down_to_common() breaks its while loop due 
to queue_has_nonstale().


  reply	other threads:[~2017-12-15 15:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 21:49 Question about the ahead-behind computation and status Jeff Hostetler
2017-12-15 10:08 ` Jeff King
2017-12-15 15:08   ` Jeff Hostetler
2017-12-15 15:43     ` Derrick Stolee [this message]
2017-12-15 18:30       ` Junio C Hamano
2017-12-15 19:40         ` Derrick Stolee

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