git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Multiple clients accessing git over NFS

From
JHJan Hudec <bulb@ucw.cz>
Date
Nov 15, 2010, 19:56 UTC
Message-ID
<20101115195641.GG30870@efreet.light.src>
In-Reply-To
<AANLkTim1bUbofDzC5HJnB--0WkT45ewbWCa25RebEgae@mail.gmail.com>
On Sun, Nov 14, 2010 at 15:42:29 -0800, Khawaja Shams wrote:
Show 6 quoted lines
> 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>
Previous: Jonathan NiederNext: Drew Northup
Message 5 of 10 in “Multiple clients accessing git over NFS”
  1. Khawaja ShamsNov 14, 2010
  2. Greg TroxelNov 14, 2010
  3. Khawaja ShamsNov 14, 2010
  4. Jonathan NiederNov 15, 2010
  5. Jan HudecNov 15, 2010
  6. Drew NorthupNov 15, 2010
  7. J. Bruce FieldsNov 15, 2010
  8. Sitaram ChamartyNov 15, 2010
  9. AlexNov 16, 2010
  10. Greg TroxelNov 14, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.