3 ms·
It would be nice if axis' were labeled, to give some sort of idea as to what the scale of things is.
by Zev 16y ago
It would be nice if axis' were labeled, to give some sort of idea as to what the scale of things is.
- icefox 16y agoUsed google charts to generate them and it while it probably lets you I couldn't figure out how to display the actual y values, only 0-100 which are also useless which was part of the reason I included the averaged times at the end of the article. This was a fun little article. No doubt someone else can come along and create a full blown in depth with every git command on different OS's showing just how much faster everything is. I knew git should be faster (as it is lots of io), just wanted some (basic) data to back it up rather than just saying it "should be" and thought this might be useful for others.
- Groxx 16y agohttp://code.google.com/apis/chart/docs/chart_params.html http://code.google.com/apis/chart/docs/chart_params.html "axis"/"axes" are at the bottom of the Parameters table. Or, have you tried the wizard?
- icefox 16y agoJust dumped the data in the wizard
- sathyabhat 16y agoyou should try Hohli [1] :) [1]: http://charts.hohli.com/ http://charts.hohli.com/
- Groxx 16y agoAgreed, though there are measurements to (nearly?) all of the graphs. 1: "The git add took around ten minutes to run on the hard drive compared to the 40 seconds for the ssd. Committing was also 1/3 of the time taking only 20 seconds v.s. over a minute." 2: "the seven seconds saved wasn't that much compared to the seven minutes the server (a slow arm based box) was preparing the repo." etc. And further down there's a chunk of the actual values. They're weird graphs in general though, with 3 statuses and text that mentions that "status" runs in 2x faster, which is only backed up by one of those status-pairs.
- CWIZO 16y agoObligatory: http://xkcd.com/833/ http://xkcd.com/833/ (today's xkcd)
- Groxx 16y agoWow, epic timing.