From: Jan Hudec <bulb@ucw.cz>
To: Khawaja Shams <kshams@usc.edu>
Cc: git@vger.kernel.org
Subject: Re: Multiple clients accessing git over NFS
Date: Mon, 15 Nov 2010 20:56:41 +0100 [thread overview]
Message-ID: <20101115195641.GG30870@efreet.light.src> (raw)
In-Reply-To: <AANLkTim1bUbofDzC5HJnB--0WkT45ewbWCa25RebEgae@mail.gmail.com>
On Sun, Nov 14, 2010 at 15:42:29 -0800, Khawaja Shams wrote:
> Hi Greg,
> Thank you for the insightful response. We have multiple automated
> clients pushing and pulling changes from git as events occur. We have
> not hit any real performance issues just yet. Our main goal is to
> improve the availability of the repository in case the box running the
> apache server has an outage during a mission critical period.
If you are out for availability, NFS isn't an answer, because the NFS server
remains a single point of failure. There are distributed filesystems
(Gluster, Lustre etc.) that can provide redundancy of storage nodes too or
you could have shared storage array with appropriate filesystem (GlobalFS,
OCFS2, etc.), but that requires special hardware. These will probably give
you better performance too -- git network protocol is optimized to send
minimal data, but that often means a lot more needs to be read from the disk.
I don't have personal experience with them though, so I can't give you more
specific recommendation.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
next prev parent reply other threads:[~2010-11-15 19:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 21:24 Multiple clients accessing git over NFS Khawaja Shams
2010-11-14 23:11 ` Greg Troxel
2010-11-14 23:42 ` Khawaja Shams
2010-11-15 0:32 ` Jonathan Nieder
2010-11-15 19:56 ` Jan Hudec [this message]
2010-11-15 20:44 ` Drew Northup
[not found] ` <AANLkTinX-XR2TaZPGPeWyekMq3e8wEDkfcmi_o6pTvMK@mail.gmail.com>
2010-11-14 23:46 ` Greg Troxel
2010-11-15 16:24 ` J. Bruce Fields
2010-11-15 1:26 ` Sitaram Chamarty
2010-11-16 13:47 ` Alex
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=20101115195641.GG30870@efreet.light.src \
--to=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=kshams@usc.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).