Re: low memory system to clone larger repo

2015-02-09 Thread matthew sporleder
Below is the output from my index-pack/clone over git:// This is with the recent memory patch applied but testing some less crazy tuning. -- The corruption of the signal number shows up in google from other people so I guess it's a lingering bug. * git-tests $ git clone git://github.com/jsonn/sr

Re: low memory system to clone larger repo

2015-02-09 Thread Duy Nguyen
On Thu, Jan 8, 2015 at 11:10 PM, matthew sporleder wrote: > I am attempting to clone this repo: https://github.com/jsonn/src/ This repo has 3.4M objects. Basic book keeping would cost 200MB (in practice it'll be higher because I'm assuming no deltas in my calculation). On my 64-bit system, it alr

Re: low memory system to clone larger repo

2015-02-09 Thread Matt Sporleder
A more "final" version of the tuning exercise I did is here: http://mail-index.netbsd.org/tech-repository/2015/01/08/msg000520.html I did try some of these setting on the server and it made the repo much much larger so I guess I am looking for ways to just reduce client memory usage/the best ba

Re: low memory system to clone larger repo

2015-02-09 Thread Duy Nguyen
On Thu, Jan 8, 2015 at 11:10 PM, matthew sporleder wrote: > I am attempting to clone this repo: https://github.com/jsonn/src/ > > and have been successful on some lower memory systems, but i'm > interested in continuing to push down the limit. > > I am getting more success running clone via https:

low memory system to clone larger repo

2015-01-08 Thread matthew sporleder
I am attempting to clone this repo: https://github.com/jsonn/src/ and have been successful on some lower memory systems, but i'm interested in continuing to push down the limit. I am getting more success running clone via https:// than git:// or ssh (which is confusing to me) and the smallest sys