Connection to Codespace is unbearably slow #34864
Replies: 3 comments 5 replies
-
Hey @brawaru! Codespaces is geographically located in four Azure regions - would you mind double checking that you aren't accidentally pinning yourself to a distant region: https://docs.github.com/en/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces. We haven't heard similar reports, but will look into latency issues with the information you've provided |
Beta Was this translation helpful? Give feedback.
-
Did you ever find a solution to this? @brawaru @sheuvembo |
Beta Was this translation helpful? Give feedback.
-
I used codesapces for 30 hours the past 2 weeks. A few times a day it would get really slow so I couldn't search for and load files quickly, or anything really. Every few days it would try to reconnect indefinitely and I'd have to stop my current codespace and restart it for it to work. Stopped using it. |
Beta Was this translation helpful? Give feedback.
-
It seems that connections to Codespaces are throttled to unbearable speeds. I have to debug JavaScript app and in development builds code chunks can reach up to 5 MB in size, which is nothing for my network connection, yet it takes 2 minutes (!!!) to load through bound port of Codespace on
localhost
.Codespaces competitor, Gitpod, doesn't seem to have this problem, from there this chunk will be downloaded before you'll snap your fingers. Sadly, they have other problems to be a viable alternative.
And even worse, while you're busy loading this chunk of JavaScript in the browser, forget about being able to save / open any files or folders in VS Code itself, the channel is too overloaded for VS Code to be able to do anything. At the end it may also complain about the ‘network delay’:
I even tried to connect with VPN from various other European countries, hoping that maybe it's my network problem, but there are zero changes expect for the terminal delay, so I doubt that's my issue. Don't think that's app's issue either, it uses less that GB of RAM and rarely reaches more than 10% CPU on any of the cores, and once again, it worked perfectly fine on Gitpod.
I really hope GitHub will address this. That's just ridiculous for the dev experience and kills a genuinely good service.
Beta Was this translation helpful? Give feedback.
All reactions