Supercharge your Git workflows
Darwin Sanoy
- Why Git Clone performance is critical
- The default is very heavy
- Yet, many things do not require the default full history
- It affects the cost of the entire chain right back to centralized remote Git services
- End point sizing
- Network sizing
- Git cloning requires programmatic response from the server level - so large workload requests drive the performance hard.
- Garbage collection and maintenance on Git clients and servers
- When is Git Clone performance critical (things that are on the rise)
- special uses cases such as scaled CI,
- remote dev environments
- scaled monorepos, polyrepos
- Binaries in repos
- GitOps "lightweight" manifest / config retrievals
- Why is Automated Benchmarking Especially helpful?
- Works in many buried environments
- Allows testing of optimizations to see if build or other processes are compatible