From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: cygwin: push/pull takes very long time
Date: Thu, 2 Mar 2006 18:09:23 +0100 [thread overview]
Message-ID: <81b0412b0603020909p179ed9bx4ed8fc2ddf77e868@mail.gmail.com> (raw)
In-Reply-To: <81b0412b0603020526w7db41994v54a96895c1a6e960@mail.gmail.com>
On 3/2/06, Alex Riesen <raa.lkml@gmail.com> wrote:
> It's still working, half an hour since it was started.
> It can be seen that it is constantly growing and shrinking
> (for about 20k,50k,80k,100k back and forth).
The distribution is (there are some git-commits and gitks
probably, here as git-read-tree?) below. The first number
after program name is lower range limit, the second - upper limit.
The number after them - counter of *alloc calls.
The strange pair 65536:99999 means very big objects, more than 1Mb.
I'll cleanup the profiling code and send it as well soon
(I had to instrument x*alloc).
git-read-tree:16:256 127002
git-rev-list:16:256 44775
git-read-tree:0:16 22577
git-pack-objects:16:256 12495
git-pack-objects:256:4096 12303
git-pack-objects:4096:65536 6929
git-diff-index:16:256 4381
git-http-fetch:16:256 3535
git-diff-index:16:256 2914
git-write-tree:4096:65536 2876
git-http-fetch:0:16 2111
git-fetch-pack:16:256 1646
git-fetch-pack:0:16 1522
git-rev-list:256:4096 1067
:16:256 976
git-read-tree:256:4096 965
git-http-fetch:256:4096 835
:0:16 825
git-ls-files:0:16 791
git-rev-list:0:16 748
git-fetch-pack:256:4096 698
git-upload-pack:16:256 610
git-pack-objects:65536:1048576 594
git-rev-parse:16:256 571
:256:4096 554
git-rev-parse:0:16 492
git-upload-pack:0:16 469
git-upload-pack:256:4096 248
git-cat-file:0:16 243
git-peek-remote:16:256 242
git-merge-base:0:16 229
git-merge-base:16:256 208
git-cat-file:16:256 167
git-rev-parse:256:4096 141
git-rev-parse:16:256 117
git-rev-parse:0:16 116
git-cat-file:256:4096 80
git-pack-objects:0:16 73
git-diff-index:0:16 65
git-merge-base:256:4096 59
git-pack-objects:65536:99999 54
git-current-branch:0:16 48
git-diff-index:0:16 47
git-diff-tree:16:256 42
git-diff-index:256:4096 36
git-unpack-objects:16:256 31
git-diff-tree:16:256 30
git-ls-files:16:256 27
git-update-index:16:256 27
git-diff-index:256:4096 24
git-write-tree:16:256 23
git-cat-file:16:256 22
next prev parent reply other threads:[~2006-03-02 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 13:26 cygwin: push/pull takes very long time Alex Riesen
2006-03-02 17:09 ` Alex Riesen [this message]
2006-03-02 21:54 ` Alex Riesen
2006-03-03 0:28 ` Christopher Faylor
2006-03-03 9:10 ` Alex Riesen
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=81b0412b0603020909p179ed9bx4ed8fc2ddf77e868@mail.gmail.com \
--to=raa.lkml@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).