From: Michael Haggerty <mhagger@alum.mit.edu>
To: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2011, #04; Tue, 12)
Date: Thu, 14 Apr 2011 17:21:31 +0200 [thread overview]
Message-ID: <4DA710FB.7060808@alum.mit.edu> (raw)
In-Reply-To: <BANLkTi=7YSfKe=Pc5n-BNr30=ADM-jRXrg@mail.gmail.com>
On 04/14/2011 03:38 PM, Piotr Krukowiecki wrote:
> On Wed, Apr 13, 2011 at 12:43 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> * mh/git-svn-automkdirs (2011-04-01) 1 commit
>> (merged to 'next' on 2011-04-03 at 7fa4978)
>> + git-svn: add an option to skip the creation of empty directories
>>
>> Should be safe, but I'd like an Ack from git-svn folks.
>
> I wanted to test performance of this change - what's the best way to do it?
>
> I tried some ideas, but rebase was too fast for performance measurements.
> I did not have new commits, but just some old, already in trunk changes, which
> I tried to rebase - probably it was just fast forward?
The unhandled.log.gz file for trunk of our main project is 14 Mb and
uncompresses to 233 Mb. About 90% of it consists of svn:mergeinfo
properties for file that were copied or renamed within the repository;
most of the rest is other random SVN file properties.
With such a huge unhandled.log file, "git svn mkdirs" took about 10s for
me. I believe that "git svn rebase" should take at least as long, even
if it is a fast-forward.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2011-04-14 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 22:43 What's cooking in git.git (Apr 2011, #04; Tue, 12) Junio C Hamano
2011-04-14 13:38 ` Piotr Krukowiecki
2011-04-14 13:50 ` Piotr Krukowiecki
2011-04-14 15:21 ` Michael Haggerty [this message]
2011-04-15 6:24 ` Piotr Krukowiecki
2011-04-15 8:31 ` Michael Haggerty
2011-04-14 18:46 ` Jakub Narebski
2011-04-14 19:14 ` 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=4DA710FB.7060808@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=piotr.krukowiecki@gmail.com \
/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).