From: Junio C Hamano <gitster@pobox.com>
To: Daniel Steinborn <daniel.steinborn@lrz.de>
Cc: git@vger.kernel.org
Subject: Re: Poor git write performance to NFS
Date: Wed, 21 Oct 2015 11:20:17 -0700 [thread overview]
Message-ID: <xmqqlhaw5bj2.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <56278FD3.3010103@lrz.de> (Daniel Steinborn's message of "Wed, 21 Oct 2015 15:14:59 +0200")
Daniel Steinborn <daniel.steinborn@lrz.de> writes:
> currently we are experiencing poor write performance when a repository
> is pushed to a nfs volume. Interestingly, this seems to be a problem
> in newer git versions:
>
> v1.7.12.4: Very good performance
>
> v2.1.4: Bad performance, up to 6 times slower
>
> Are there any changed default settings or new features that can be the
> reason for that problem?
>
> Please ask for specific details if they are neccessary.
Between 1.7.12.x series and v2.1.4, there are more than two years'
worth of changes, so it is unreasonable for anybody to expect that
such a question can be answered in a meaningful way.
Have you tried more recent versions yet? 2.1.x series is over a
year old, and I am reasonably sure there have been tons of "earlier
we did X for correctness, which unfortunately made things slower,
and this ensures the same correctness in a different way that is
much more performant" fixes since then.
next prev parent reply other threads:[~2015-10-21 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 13:14 Poor git write performance to NFS Daniel Steinborn
2015-10-21 18:20 ` Junio C Hamano [this message]
2015-10-22 13:04 ` Daniel Steinborn
2015-10-22 16:07 ` Junio C Hamano
2015-10-22 16:11 ` Jeff King
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=xmqqlhaw5bj2.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=daniel.steinborn@lrz.de \
--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 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.