Re: [git-users] git on nfs is outrageously slow

2013-08-14 Thread dexter ietf 
 That's exactly what I do. I have my bare repository on an NFS mounted 
filesystem, but my working directory on my local disk. It works well for me.

hi john, can you explain me what do you mean by the above statement,
what's the workflow. do you clone only part of the tree to your local
disk ?

On Wednesday, July 31, 2013 5:36:41 PM UTC+5:30, John McKown wrote:






-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [git-users] git on nfs is outrageously slow

2013-08-14 Thread John McKown 
Actually, I start with my working directory. One person shop (not a
business). But basically, my working directory has everything. I just do
git push commands as needed as a form of backing up my working directory
to my NAS box. Also, I have a machine at work. And I modify and test files
there as well. The work machine's repository accesses the NAS box though
the home PC, going to the NAS box. When I decide to stop work on my PC at
work, I do the git add, git commit and git push to push everything to
my NAS box. When I get home, I do a git pull to pull all the changes to
my home machine and continue working there. And vice versa when I go from
home to work.


On Wed, Aug 14, 2013 at 10:14 AM, dexter ietf dexter.i...@gmail.com wrote:

  That's exactly what I do. I have my bare repository on an NFS mounted
 filesystem, but my working directory on my local disk. It works well for me.

 hi john, can you explain me what do you mean by the above statement,
 what's the workflow. do you clone only part of the tree to your local
 disk ?

 On Wednesday, July 31, 2013 5:36:41 PM UTC+5:30, John McKown wrote:




  --
 You received this message because you are subscribed to the Google Groups
 Git for human beings group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to git-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.






-- 
As of next week, passwords will be entered in Morse code.

Maranatha! 
John McKown

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [git-users] git on nfs is outrageously slow

2013-08-01 Thread dexter ietf 
On Wednesday, July 31, 2013 5:36:41 PM UTC+5:30, John McKown wrote:

 That's exactly what I do. I have my bare repository on an NFS mounted 
 filesystem, but my working directory on my local disk. It works well for me.

 Also, what is the speed between the local machine and the NFS server? I 
 have a gigabyte connection on a LAN. Also, how busy is the NFS server? What 
 else is running on the same server? How many concurrent users are there and 
 what are they doing? As you may have guessed, I am wondering if the problem 
 is the server or the connection to the server, rather than git itself.

 On Wed, Jul 31, 2013 at 6:39 AM, Johannes Müller 
 dersinnd...@gmx.netjavascript:
  wrote:

 You can make a local clone of your git repository and use the nfs git
 repository to push your changes to. This way you get to work with git
 with normal speed and only when pushing, there is a speed penalty.
 Otherwise, you could try to configurate nfs so that it caches access to
 the file. Note that afaik nfs might cause problems when you access the
 same file simultaneously with several users because it does not support
 locking a file.

 Johannes

 On 31.07.2013 13:01, dexter ietf wrote:
  please help on fixing it, it is so slow that i started hating git (for
  wrong reasons)
  i'm sure there is a way out, please help me to make my git faster.
 
  -dexter
 
  --
  You received this message because you are subscribed to the Google
  Groups Git for human beings group.
  To unsubscribe from this group and stop receiving emails from it, send
  an email to git-users+...@googlegroups.com javascript:.
  For more options, visit https://groups.google.com/groups/opt_out.
 
 

 --
 You received this message because you are subscribed to the Google Groups 
 Git for human beings group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to git-users+...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/groups/opt_out.




the nfs server is from my company, cloning the tree to a local disk is good 
idea,
but i'd loose the backup functionality that nfs provides, and the build 
environment
is present in the nfs server as well, i'm not sure how can i get around 
this, or can
i clone the tree from my nfs tree. will the following scheme work ? are 
there any
documentation to do the same.


origin/master 
|
|
nfs server --- clone a tree here. t1 -- (build here)
|
|
local disk --- clone from t1, (work here, push to t1)

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.