git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Berov <vitaly.berov@gmail.com>
To: git@vger.kernel.org
Cc: git@vger.kernel.org
Subject: Re: git clone: very long "resolving deltas" phase
Date: Fri, 09 Apr 2010 10:50:44 +0400	[thread overview]
Message-ID: <4BBECE44.4040608@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1004070842580.7232@xanadu.home>

Hi,

On 04/07/2010 04:55 PM, Nicolas Pitre wrote:
>
> I was asking that because that would have helped me (or any other Git
> developer) analyse the issue and provide a fix.
>
> OK then.  What happens if you do the following on the server machine
> where the repository is stored:
>
> 	git repack -a -f -d
>
> How long does this take?
>
> How long does the "Resolving deltas" take when cloning this repacked
> repository? (don't wait more than 10 minutes for it).
Nicolas, we haven't stopped the process as you recommended, sorry for that.

So, the results: it took 37 hours. 20 hours is compressing objects 
(delta compression using up to 4 threads), 17 hours is writing objects. 
Almost all of the time the bottleneck was a CPU.

Objects amount: 3997548.
Size of the repository: ~57Gb.

> If the "Resolving deltas" takes more than 10 minutes, could you capture
> a strace dump from that process during a minute or so and post it here?
I'll capture strace later.

> Hmmm. Is this on Linux or Windows?
Short spec: Ubuntu 9.04 (64 bit), Intel(R) Core(TM)2 Quad CPU Q8400 
2.66GHz, 8 GB of memory

By the way, we have a large amount of binary files in our rep.

Vitaly

  reply	other threads:[~2010-04-09  6:55 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 14:18 git clone: very long "resolving deltas" phase Vitaly Berov
2010-04-06 15:01 ` Matthieu Moy
2010-04-06 15:28   ` Vitaly Berov
2010-04-06 15:29   ` Vitaly
2010-04-06 15:32     ` Andreas Ericsson
     [not found]       ` <q2mec874dac1004060850r5eaa41fak2ba9889d07794651@mail.gmail.com>
2010-04-06 15:56         ` Vitaly Berov
2010-04-06 21:09           ` Nicolas Pitre
2010-04-07  5:54             ` Vitaly Berov
2010-04-07  8:00               ` Ilari Liusvaara
2010-04-07  8:14                 ` Vitaly
2010-04-07  9:00                   ` Ilari Liusvaara
2010-04-07  9:37                   ` Jakub Narebski
2010-04-07 14:20                   ` Nicolas Pitre
2010-04-07 14:35                     ` Vitaly
2010-04-07 14:55                       ` Nicolas Pitre
2010-04-09  6:46                         ` Vitaly Berov
2010-04-09 19:30                           ` Nicolas Pitre
2010-04-10  6:32                             ` Vitaly Berov
2010-04-07 14:08                 ` Nicolas Pitre
2010-04-07 14:29                   ` Sverre Rabbelier
2010-04-07 14:37                     ` Vitaly
2010-04-07  5:55             ` Vitaly
2010-04-07 12:42               ` Nicolas Pitre
2010-04-06 21:05       ` Nicolas Pitre
2010-04-07  9:22         ` git clone: very long &quot;resolving deltas&quot; phase Marat Radchenko
2010-04-07 14:40           ` Nicolas Pitre
2010-04-06 21:01   ` git clone: very long "resolving deltas" phase Nicolas Pitre
2010-04-06 21:10 ` Nicolas Pitre
2010-04-07  5:57   ` Vitaly
2010-04-07 12:55     ` Nicolas Pitre
2010-04-09  6:50       ` Vitaly Berov [this message]
2010-04-09  8:13         ` Matthieu Moy
2010-04-09 19:18           ` Nicolas Pitre
2010-04-10  8:05           ` Vitaly Berov
2010-04-09 19:25         ` Nicolas Pitre
2010-04-10  7:58           ` Vitaly Berov
2010-04-10 13:25       ` Vitaly Berov
2010-04-11  0:50         ` Nicolas Pitre
2010-04-12 15:31           ` Vitaly

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=4BBECE44.4040608@gmail.com \
    --to=vitaly.berov@gmail.com \
    --cc=git@vger.kernel.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 NNTP newsgroup(s).