All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Heidelberg <markus.heidelberg@web.de>
To: git@vger.kernel.org, Eric Wong <normalperson@yhbt.net>
Subject: "git svn fetch" slow
Date: Sat, 31 Jan 2009 14:14:57 +0100	[thread overview]
Message-ID: <200901311414.58205.markus.heidelberg@web.de> (raw)

Hi,

since several days "git svn fetch" didn't seem to work any more. I
bisected it down to

    commit dbc6c74d0858d77e61e092a48d467e725211f8e9
    git-svn: handle empty files marked as symlinks in SVN
    2009-01-11

In the new function _mark_empty_symlinks() there is a loop that takes
about 36 seconds for me. That means each svn revision takes 36+x seconds
for downloading. So it still works, but I aborted it before waiting so
much time, so I thought, it didn't work any more.

The loop loops over each blob ("git ls-tree -r git-svn | wc -l" times).
The project I'm using git-svn with is Buildroot and it has currently
3074 blobs in the tree. Printing a loop counter every time the loop is
executed, I can see that it mostly goes really fast, but there are
files, where it needs much time then.

Could there be a way to avoid this time consuming step?

Markus

             reply	other threads:[~2009-01-31 13:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31 13:14 Markus Heidelberg [this message]
2009-01-31 16:23 ` "git svn fetch" slow Sverre Rabbelier
2009-01-31 17:01   ` Markus Heidelberg
2009-01-31 17:31     ` Sverre Rabbelier
2009-02-01  2:18 ` [PATCH] git-svn: allow disabling expensive broken symlink checks Eric Wong
2009-02-02  3:03   ` Junio C Hamano
2009-02-03  4:45     ` Eric Wong
2009-02-03  6:52       ` Junio C Hamano
2009-02-03 19:10         ` Eric Wong
2009-02-05  7:42           ` Eric Wong
2009-02-05  8:02             ` Junio C Hamano

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=200901311414.58205.markus.heidelberg@web.de \
    --to=markus.heidelberg@web.de \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.