git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
	Michael Haggerty <mhagger@alum.mit.edu>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2011, #04; Tue, 12)
Date: Thu, 14 Apr 2011 15:50:53 +0200	[thread overview]
Message-ID: <BANLkTin6=b9E=2gBjsWd+Y9Fg-APR1xOgw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=7YSfKe=Pc5n-BNr30=ADM-jRXrg@mail.gmail.com>

On Thu, Apr 14, 2011 at 3:38 PM, Piotr Krukowiecki
<piotr.krukowiecki@gmail.com> 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?

I found some old not-yet-rebased branch (with 3 commits) and tried rebasing it.
I saw no time difference - maybe I'm doing it wrong?

I did following for both true and false config setting:

git checkout -b test_rebase old_branch
time git svn rebase
git checkout master
git branch -D test_rebase
<repeat>

Results I got:
13.7s 13.4s 13.6s (config: false)
13.6s 13.6s 16.6s (config: true)

The last "true" result is higher because rebase had to fetch one new revision.


-- 
Piotr Krukowiecki

  reply	other threads:[~2011-04-14 13:51 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 [this message]
2011-04-14 15:21   ` Michael Haggerty
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='BANLkTin6=b9E=2gBjsWd+Y9Fg-APR1xOgw@mail.gmail.com' \
    --to=piotr.krukowiecki@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mhagger@alum.mit.edu \
    /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).