-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very long activation time #23
Comments
Welcome!Thank you for finding time to write an issue and help to make this extension better. I`ll appreciate if you find some time to rate this extension here. I`ll get to this Issue ASAP. |
This extension requires Git and Git-base core extensions you can see it in extension details page. It means that extension will not start activation until SCM is loaded. So, first after you launch VS Code it waits until SCM section loads and then it loads itself. After CSM is loaded it might take a second, but after VS Code launch it will be definitely longer. Anyway, thank you for nothing. If you like this extension, I'll appreciate if you rate it here |
Sorry, but with Git Flow extension disabled the SCM section loads in half the time (7sec vs 14sec). |
What 14s? |
Yes but it is not the absolute value the problem, it is the difference. If it should take 1 sec more after the SCM is loaded it should be 8sec. |
I'll try to check a performance. |
I've created a small test with time measurements. It turns out that delay is command I'll think how I can optimize this. |
Also if ORIGIN exists it pulls all tags from it
Also all branches
|
And it depends on how many branches, tags, ecc the repo has, I think. I can try with a very simple repo. |
It might also depend on your connection speed. Give me 3 minutes I'll release new version where in the log you can see time what took most of the time. |
https://github.com/Serhioromano/vscode-gitflow/actions |
Mmmm yes today I work from home through VPN, I will try next time in the office. |
Published. Give marketplace 2-3 minutes to approve. Version 1.3.3. Open OUTPUT and Git Flow stream, there should a time for every git command. Tell me what takes time. |
OK, thanks I will try and give you a feedback here. |
Any result? |
Yes, more or less 6 sec less. Well done! Thanks! |
Do not forget to rate. I need it badly. Very hard to get ranged in the beginning. |
Already done ;) |
Hi, |
Hmmmm, I am going to look into it when I come back home from trip. |
Due to gitflow extension my git repo detection under git tab takes very log time ~10s |
I think it is because Git Flow also fetch remote branches if your repo have long history or many files it might take few seconds. |
My gitflow takes a long time, in operations like creating start feature, start hotfix, I'm windows. Any suggestions on how to improve performance. |
Do you work in WSL? |
No. I'm on windows. |
What is your repository? Is the size is big? You have HDD or SSSD? |
My repository is small, it has only one class. My PC is SSD. To make a git flow init, it takes 6 minutes |
Ha a delay too when you switch branches |
You mean delay when you run |
You're right. When I run git commands it's super fast, but when I run commands from the git flow extension, it's very slow. Any tips to make it faster? |
Git commands or gitflow commands? I am sorry but I cannot reproduce it. |
Hi,
the extension is good, but it takes a lot of time to activate:
Is this normal? Does it depend by the repo complexity?
Thanks
The text was updated successfully, but these errors were encountered: