This not only makes most operations much faster than you may be used to, but it also allows you to work on stuff offline. That may not sound like a big deal, but I'm always amazed at how often I actually do work offline. Being able to branch, merge, commit and browse history of your project while on the plane or train is very productive. Even in Mercurial, common commands like 'incoming' and 'outgoing' hit the server, whereas with Git you can 'fetch' all the servers data before going offline and do comparisons, merges and logs of data that is on the server but not in your local branches yet.
This means that it's very easy to have copies of not only your branches, but also of everyone's branches that are working with you in your Git repository without having to mess your own stuff up. Git is fast. Everyone—even most of the hard core users of these other systems—generally give Git this title.
With Git, all operations are performed locally giving it a bit of a leg up on SVN and Perforce, both of which require network access for certain operations. Part of this is likely because it was built to work on the Linux kernel, which means that it has had to deal effectively with large repositories from day one.
Additionally, Git is written in C, reducing the overhead of runtimes associated with higher-level languages. Another reason that Git is so fast is that the primary developers have made this a design goal of the application. The following are a number of benchmarks that I performed on three copies of the Django source code repository in 3 different SCMs: Git, Mercurial and Bazaar.
I also tested some of this stuff in SVN, but trust me, it's slower—basically take the Bazaar numbers and then add network latency The end result was that for everything but adding new files, Git was fastest.
Also really large commits, which Hg was basically the same at, but the commit I tested was so large that you're unlikely to ever do anything like it—normal commits are much faster in Git. The cold and hot branching numbers are the numbers for the first and second times that I branched a repo—the second number being a branch with a hot disk cache.
It should be noted that although the 'add' numbers are much slower, this was for a massive add operation—over files. For the majority of what most people do on a daily basis, add ops in any of these systems will only take a fraction of a second. All of the other ops tested here except for the large commit, possibly are more indicative of things you might actually do day to day. These numbers are really not difficult to recreate, simply clone the Django project in each of the systems and try out the same commands in each.
Git is really good at conserving disk space. Your Git directory will in general barely be larger than an SVN checkout—in some cases actually smaller apparently a lot can go in those. The following numbers were taken from clones of the Django project in each of its semi-official Git mirrors at the same point in its history.
Unlike the other systems, Git has what it calls the "staging area" or "index". This is an intermediate area that you can setup what you want your commit to look like before you commit it. The cool thing about the staging area, and what sets Git apart from all these other tools, is that you can easily stage some of your files as you finish them and then commit them without committing all the modified files in your working directory, or having to list them on the command line during the commit.
Write a review. Add new review: Enter your review here. Your Name:. Your E-mail:. Share review on Facebook? Submit review. Technical information The web server used by Whygitisbetterthanx. On this web server 13 other websites are hosted. The language of those websites is mostly english. Only a few websites on this web server are x-rated. You can discover similar sites based on what tags they have and how important they are for your search.
Click on the tags to edit them, and use the sliders to adjust their importance. The tags shown right now are the top 5 tags of the URL you just searched for. Hit "moreofit" to see results. If you are just after tracking someone else's project, this get you started In those small tables, at the left we always list the Git commands for the task, And woe unto thee if a rule is broken somewhere along the way, or you In simplified form, git object storage is "just" a DAG of objects, with a handful of Probably Git's most compelling feature that really makes it stand apart from It is completely different from all of the models I'm comparing it to here, most So you're chugging along developing in a topic branch when you decide it's about Our open-source work is stored in git repositories, but our client work is still The integration between git and Subversion git-svn is so well done that This slider determines how the matched sites are sorted.
0コメント