This repository has been archived by the owner on Sep 11, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 543
As a server Shortcuts/Optimisations? #627
Labels
Comments
Out of curiosity I tested piping to and from git-upload-pack
This is the result I was kinda hoping for, but I'd still be happy with githubish speed |
The problem is that the packfile is being calculated and all the deltas, and this is expensive operation. |
Just a bit more information about the evolution of the problem: The baseline a git server local server serving the example repository of git cloneBaseline, git daemon (0:04.80elapsed)
After #697 (1:10.97elapsed)
Before #697 (2:28.55elapsed)
git fetch origin v0.6.0Baseline, git daemon (0:00.98elapsed):
After #697 (0:11.95elapsed)
Before #697 (0:19.10elapsed)
|
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi
I'm trying to write a caching proxy server that we can use to cache locally various repos from github (and other places) that we use heavily but I'm running into a performance issue
I'm more than happy to concede that we won't beat
github
for speed but I'm finding this to be a great deal slower.This is a greatly simplified version of what I'm running in the main codebase
if you clone the aws/aws-sdk-go repo
git clone --quiet --mirror https://github.com/aws/aws-sdk-go aws-sdk-go
into the same directory as you put this go fileThen
go run main.go
you can do the following testsThe time cost here is entirely in cloning from scratch, pulling seems plenty fast.
I did profile my code and I found it spent most of it's time in encoder.go
Can anyone think of any way to shortcut this process for a clone if not optimise the code?
If instead of using git clone --mirror to create the aws-sdk-dir and I use go-git to clone it I even get pre-packed files
Perhaps for a fresh clone I can just ship that?
The text was updated successfully, but these errors were encountered: