A git clone is just too slow right now the way its setup. So what will be done to fix that? Currently, svn is way faster in the worst case. In the time it takes to git clone, i can do 10 svn checkouts.
I sometimes use git, but usually when working on software, i don't work on trivial things. I do nontrivial stuff and sometimes shit breaks, including git workspaces and including git itself. On average do I get > 10 branches per clone() ? Not sure. I dont know if its because there used to be JAR files in the source trees back in the day or what, but fixing this is really mandatory. Remember for a new developer its also something they must always do, so its not just when 'git fucks up for me', it is a slow operation that occasionally people must deal with. And its just too slow. git clone: Cloning into 'lucene-solr'... remote: Counting objects: 563630, done. remote: Compressing objects: 100% (136240/136240), done. remote: Total 563630 (delta 329023), reused 539045 (delta 304604) Receiving objects: 100% (563630/563630), 356.90 MiB | 1.79 MiB/s, done. Resolving deltas: 100% (329023/329023), done. Checking connectivity... done. real 3m43.157s user 0m38.243s sys 0m10.480s svn co: Checked out revision 1682598. real 0m34.713s user 0m5.504s sys 0m4.170s PS don't tell me i dont know how to use git correctly, i dont care to hear your religious arguments. A clone is still the worst case operation, so it must be supported. Its also the first thing someone must do, if they want to work with the codebase. And with git right now, its broken (too slow) for lucene-solr. On Fri, May 29, 2015 at 5:07 PM, Anshum Gupta <ans...@anshumgupta.net> wrote: > I know this has come up a few times in the past but I wanted to bring this > up again. > > The lucene-solr ASF git mirror has been behind by about a day. I was > speaking with the infra people and they say that the size of the repo needs > more and more ram. Forcing a sync causes a fork-bomb: > > Can't fork: Cannot allocate memory at /usr/share/perl5/Git.pm line 1517. > > They tried a few things but it's almost certain that it needs even more RAM, > which still is a band-aid as they'd soon need even more RAM. Also, adding > RAM involves downtime for git.a.o which needs to be planned. As a stop gap > arrangement attached a volume to the instance and are using it as swap to > work around the "adding RAM requires restart" issue. > > FAQ: How would the memory requirement change if we moved to git instead of > mirroring? > Answer: svn -> git mirroring is a weird process and has quite the memory > leak. Using git directly is much cleaner. > > I personally think git does make things easier to manage when you're working > on multiple overlapping things and so we should re-evaluate moving to it. I > would have been fine had the mirroring worked, as all I want is a way to be > able to work on multiple (local) branches without having to create and > maintain directories like: lucene-solr-trunk1, lucene-solr-trunk2, or > SOLR-XXXX, etc. > > Opinions? > > > -- > Anshum Gupta --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
