Skip to content

Instantly share code, notes, and snippets.

View colossus9's full-sized avatar
:shipit:
Ship to Learn

James Garcia colossus9

:shipit:
Ship to Learn
View GitHub Profile
@colossus9
colossus9 / Jenkinsfile
Created January 19, 2017 16:18 — forked from chinshr/Jenkinsfile
Best of Jenkinsfile, a collection of useful workflow scripts ready to be copied into your Jenkinsfile on a per use basis.
#!groovy
# Best of Jenkinsfile
# `Jenkinsfile` is a groovy script DSL for defining CI/CD workflows for Jenkins
node {
}
@colossus9
colossus9 / README.md
Created October 25, 2018 10:18 — forked from hofmannsven/README.md
My simply MySQL Command Line Cheatsheet
@colossus9
colossus9 / git_speed.md
Last active April 3, 2019 02:06 — forked from emanuelez/git_speed.md
Git Speed

How Fast is Git?

The web is full of benchmarks showing the supernatural speed of Git even with very big repositories, but unfortunately they use the wrong variable. Size is not important, but the number of files in the repository really is!

Why is that? Well, that's because Git works in a very different way compared to Synergy. You don't have to checkout a file in order to edit it; Git will do that for you automatically. But at what price?

The price is that for every Git operation that requires to know which files changed (git status, git commmit, etc etc) an lstat() call will be executed for every single file

Wow! So how does that perform on a fairly large repository? Let's find out! For this example I will use an example project, which has 19384 files in 1326 folders.