I wrote something a few years ago that does a similar thing using a real command line. https://github.com/Gazler/githug
The truth is both are blazing fast, but at least on my machine git status is a hair faster:
$ mkdir baz
$ cd baz
$ time git init
Initialized empty Git repository in ~/src/tmp/baz/.git/
real 0m0.015s
user 0m0.002s
sys 0m0.008s
$ time git status
# On branch master
#
# Initial commit
#
nothing to commit (create/copy files and use "git add" to track)
real 0m0.012s
user 0m0.002s
sys 0m0.003sInterestingly, for me git init took 0.045s, while status took 0.005s. I wonder what factors into this.
For an existing repository: Size of the repository, as well as the number of files in the folder. A single git status on a 1.7GB git repository takes about 9 seconds with a warm disk cache on my workstation.
Re:Try Git
by farnsworth on Wednesday November 26, 2014 @12:02PM
(#8663268)
It's all very slow for me right now - every command hits the server, which is disappointing.
Re:Try Git
by insertnickname on Wednesday November 26, 2014 @11:55AM
(#8663205)
Maybe it's just slow... `git status` should be quick in an empty repo.
Unfortunately, there is no tab autocompletion, which makes it really a hassle to enter "git add [specific file]" and similar commands.
I also like the idea of simulating the timing, such that the commands don't always return immediately.
However, I'm a bit surprised about the exact timing values. For example, "git init" took quite some time while "git status" was really quick. In reality, it is the other way around.