Find answers from the community

Updated 2 months ago

Forking

Is it just me, or is there something about the llamaindex git repo that makes forking/cloning it really slow?
L
N
13 comments
Hmmm tbh I've never noticed. But I think it may be a one time cost on the first clone/fork
well, like the github repo is still cloning and its clocking in at 360MB so far, so and that's just the master branch
Hmmm did we accidently commit a large file? That does seem pretty excessive πŸ€”
I mostly use perforce, so im not sure if there are things people are suppose to compact it over time, as an update it's now up to 800mb
check your .git folder size
Plain Text
(llama-index) (base) loganmarkewich@Logans-MBP llama_index % du -sh .git
 96M    .git
mines even lower if i sync it directly
I tried doing pipenv install -e git+https://github.com/nickdarnell/llama_index.git#egg=llama_index, and it's gone crazy some how
lol what is happenninggg

Lemme try a fresh clone just to sanity check
Plain Text
(llama-index) (base) loganmarkewich@Logans-MBP test_clone % git clone https://github.com/jerryjliu/llama_index.git
Cloning into 'llama_index'...
remote: Enumerating objects: 22584, done.
remote: Counting objects: 100% (7408/7408), done.
remote: Compressing objects: 100% (923/923), done.
remote: Total 22584 (delta 6713), reused 6575 (delta 6481), pack-reused 15176
Receiving objects: 100% (22584/22584), 58.14 MiB | 2.06 MiB/s, done.
Resolving deltas: 100% (15472/15472), done.
(llama-index) (base) loganmarkewich@Logans-MBP test_clone % du -sh ./llama_index 
143M    ./llama_index
(llama-index) (base) loganmarkewich@Logans-MBP test_clone % cd llama_index 
(llama-index) (base) loganmarkewich@Logans-MBP llama_index % pip install -e .
...
Successfully installed llama-index-0.7.13
(llama-index) (base) loganmarkewich@Logans-MBP llama_index % du -sh ../llama_index 
143M    ../llama_index
Add a reply
Sign up and join the conversation on Discord