From: Jens Axboe <jaxboe@fusionio.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Zdenek Kabelac <zdenek.kabelac@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Theodore Tso <tytso@mit.edu>
Subject: Re: regression - slow git rebase performance with 2.6.39-rcX kernel
Date: Tue, 12 Apr 2011 15:07:23 +0200 [thread overview]
Message-ID: <4DA44E8B.9040101@fusionio.com> (raw)
In-Reply-To: <BANLkTimAvqT0MxPWvQH6ga698TYhCXF3CQ@mail.gmail.com>
On 2011-04-12 14:51, Pekka Enberg wrote:
> Hi,
>
> [ Fixed your empty CC list. ]
>
> On Tue, Apr 12, 2011 at 3:45 PM, Zdenek Kabelac
> <zdenek.kabelac@gmail.com> wrote:
>> I'm noticing quite slower speed of my git rebase commands on my git
>> tree compared with 2.6.38 kernel.
>> I've T61 with SSD disc drive, ext4 fs, and by default deadline disk
>> io scheduler
>> The counter showing the number of 'rebased' patches on top of master
>> is going much slower.
>> When I boot 2.6.38 kernel it's much faster.
>>
>> Is it a known problem - or do I need to make a bisect ?
>
> No, I don't think it's a known problem. Git bisect would be helpful,
> obviously.
Definitely, interesting. Bisect would help. I'll try a similar workload
here and see if I see any differences. How big is your rebase, and what
are the runtimes (approximately) on .38 vs .39-rc?
--
Jens Axboe
next prev parent reply other threads:[~2011-04-12 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 12:45 regression - slow git rebase performance with 2.6.39-rcX kernel Zdenek Kabelac
2011-04-12 12:51 ` Pekka Enberg
2011-04-12 13:07 ` Jens Axboe [this message]
2011-04-12 13:59 ` Zdenek Kabelac
2011-04-12 14:00 ` Jens Axboe
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=4DA44E8B.9040101@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=zdenek.kabelac@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 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.