Epic: more regional workspace clusters #7489

kylos101 · 2022-01-06T19:06:44Z

Summary

Add workspace-clusters to more regions, we currently use two (europe-west and us-west).

Identity regions needing workspace-clusters

Context

Customers with high latency are less likely to adopt or continue using Gitpod.

Depending on where you live in the world, latency can be so high that adopting Gitpod is not possible due to latency as a result of distance from the existing EU or US clusters. Further, adoption may be possible, but retention may not because its "just" not quite fast enough. In other words, fast enough to 'check out' but not 'consistently use'.

Test your own latency to regions:

Test your latency across GCP regions, load the page, wait 10s, scroll to bottom, click stop, then sort by mean
What is your latency like in europe-west, us-west, asia-southeast, and asia-south? A mean > 100ms is not ideal.

Additional context:
Prior issue
Related epic from Meta to simplify multi-meta

Value

Users will be more likely to adopt and continue using Gitpod saas because the speed is conducive to a good user experience. For example, as you type quickly, you expect to see those characters instantly.

Acceptance criteria

New workspace clusters are

Functional in new target regions
Connected to a meta cluster in the new target region (this will ensure a good dashboard experience)
Observed by our monitoring

Measurement

Adoption and retention for customers location in regions who currently lack workspace clusters will increase.

Growth Area

Adoption - new customers will be more likely to try Gitpod because its not slow on first use
Retention - customers who adopt Gitpod will continue using because it is just as fast as applications on their local machine

Hypothesis

If we add workspace-clusters to new regions, users will be more likely to adopt and continue using Gitpod in those regions.

Complexities

Do we need to deploy meta to these regions? For adoption, no, but for retention, probably. Otherwise dashboard usage will not be ideal.
- Short term, if we wanted to run an experiment, perhaps we could deploy to another region and connect to meta in EU or US. @csweichel wdyt?
How will monitoring work for workspace-clusters in new regions?
- @meysholdt @mads-hartmann can you help set our expectations? It looks like we have a single instance of our monitoring in europe-west, therefore I assume we would not need additional instances of monitoring in new regions to support new workspace-clusters running?
Depending on our forecasted usage for the new region, and the cost for nodes in other regions, we may want to consider using a size other than our default.

Front conversations


on ⛵ gke_self-hosted-tarun_asia-east1_gitpod  ~ on ☁️  [email protected] 
❯ ping -c 10  gitpodio-gitpod-1osgnsetjzz.ws.tarun.gitpod-self-hosted.com
PING gitpodio-gitpod-1osgnsetjzz.ws.tarun.gitpod-self-hosted.com (35.229.210.95) 56(84) bytes of data.
64 bytes from 95.210.229.35.bc.googleusercontent.com (35.229.210.95): icmp_seq=1 ttl=110 time=92.3 ms
64 bytes from 95.210.229.35.bc.googleusercontent.com (35.229.210.95): icmp_seq=2 ttl=110 time=92.7 ms
64 bytes from 95.210.229.35.bc.googleusercontent.com (35.229.210.95): icmp_seq=3 ttl=110 time=91.1 ms
64 bytes from 95.210.229.35.bc.googleusercontent.com (35.229.210.95): icmp_seq=4 ttl=110 time=90.1 ms
64 bytes from 95.210.229.35.bc.googleusercontent.com (35.229.210.95): icmp_seq=5 ttl=110 time=93.6 ms
64 bytes from 95.210.229.35.bc.googleusercontent.com (35.229.210.95): icmp_seq=6 ttl=110 time=91.8 ms
64 bytes from 95.210.229.35.bc.googleusercontent.com (35.229.210.95): icmp_seq=7 ttl=110 time=89.8 ms
64 bytes from 95.210.229.35.bc.googleusercontent.com (35.229.210.95): icmp_seq=8 ttl=110 time=89.9 ms
64 bytes from 95.210.229.35.bc.googleusercontent.com (35.229.210.95): icmp_seq=9 ttl=110 time=103 ms
64 bytes from 95.210.229.35.bc.googleusercontent.com (35.229.210.95): icmp_seq=10 ttl=110 time=90.2 ms

--- gitpodio-gitpod-1osgnsetjzz.ws.tarun.gitpod-self-hosted.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9011ms
rtt min/avg/max/mdev = 89.848/92.431/102.794/3.666 ms

on ⛵ gke_self-hosted-tarun_asia-east1_gitpod  ~ on ☁️  [email protected] 
❯ ping -c 10 gitpodio-gitpod-itpc6y1mcb6.ws-us30.gitpod.io 
PING gitpodio-gitpod-itpc6y1mcb6.ws-us30.gitpod.io (34.105.101.238) 56(84) bytes of data.
64 bytes from 238.101.105.34.bc.googleusercontent.com (34.105.101.238): icmp_seq=1 ttl=105 time=229 ms
64 bytes from 238.101.105.34.bc.googleusercontent.com (34.105.101.238): icmp_seq=2 ttl=105 time=253 ms
64 bytes from 238.101.105.34.bc.googleusercontent.com (34.105.101.238): icmp_seq=3 ttl=105 time=202 ms
64 bytes from 238.101.105.34.bc.googleusercontent.com (34.105.101.238): icmp_seq=4 ttl=105 time=297 ms
64 bytes from 238.101.105.34.bc.googleusercontent.com (34.105.101.238): icmp_seq=5 ttl=105 time=203 ms
64 bytes from 238.101.105.34.bc.googleusercontent.com (34.105.101.238): icmp_seq=6 ttl=105 time=202 ms
64 bytes from 238.101.105.34.bc.googleusercontent.com (34.105.101.238): icmp_seq=7 ttl=105 time=274 ms
64 bytes from 238.101.105.34.bc.googleusercontent.com (34.105.101.238): icmp_seq=8 ttl=105 time=290 ms
64 bytes from 238.101.105.34.bc.googleusercontent.com (34.105.101.238): icmp_seq=9 ttl=105 time=216 ms
64 bytes from 238.101.105.34.bc.googleusercontent.com (34.105.101.238): icmp_seq=10 ttl=105 time=203 ms

--- gitpodio-gitpod-itpc6y1mcb6.ws-us30.gitpod.io ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9000ms
rtt min/avg/max/mdev = 201.722/236.953/297.339/36.487 ms

A min of 201 ms is definitely not ideal! :)

andymac4182 · 2022-02-17T22:21:03Z

For me in Australia the only regions from GCP that get under 100ms were the Australian regions which for Data Sovereignty issues I would love as well. Otherwise the next best based on mean is asia-southeast2

bbhxwl · 2022-05-11T06:58:03Z

I am in China and hope to have Hong Kong, Taiwan, Japan or Singapore

stale · 2022-08-11T21:19:25Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

andymac4182 · 2022-08-29T05:21:19Z

I think this needs to be reopened

ghuntley · 2022-09-08T08:54:05Z

This needs reopening

pawlean · 2022-09-08T10:12:18Z

Hey @ghuntley! This issue is open 🙌 Unless I'm misunderstanding what you mean something else? 🦩

loujaybee · 2022-09-08T10:17:18Z

There seems to be some confusion relating to the closing of the following issues:

Please note: This is not a an update of the status of this issue (closing or opening). The reason for the consolidation is that we now have a proliferation of different regional issues being raised by users. It doesn't make sense for users to directly raising issues about specific required regions, as when it comes to rolling out new regions we'll need to review:

Costings
Latencies
Current + predicted future usage of Gitpod

...and many other factors.

It makes sense for this conversation to happen in a single issue, which is this one. Please continue to share any thoughts or feedback. We'll look to update the description soon as a consolidation of current thinking, as there are now multiple region related issues with many comments.

Thanks all 🙏

robguy21 · 2022-10-13T11:20:56Z

+1 forsouthafricanorth or af-south 😬 Would love to dodge the 190+ ping without needing to self-host

xzmeng · 2022-11-17T00:49:22Z

Can't believe there's still no progress on this issue after nearly a year and a half, I've heard a gitpod ex-employee complain about high latency pain within your team (in Asia Pacific or Oceania) . What I really can't understand is that this requirement is to simply deploy an additional k8s cluster in another data center of GCP, but the gitpod team seems to have no motivation to do this at all. Is it because the number of users in APAC is too small to be profitable？

bbhxwl · 2022-11-17T01:40:51Z

Can't believe there's still no progress on this issue after nearly a year and a half, I've heard a gitpod ex-employee complain about high latency pain within your team (in Asia Pacific or Oceania) . What I really can't understand is that this requirement is to simply deploy an additional k8s cluster in another data center of GCP, but the gitpod team seems to have no motivation to do this at all. Is it because the number of users in APAC is too small to be profitable？

Very good. I support what you said.

smacintyre · 2022-11-17T01:43:03Z

Can't believe there's still no progress on this issue after nearly a year and a half, I've heard a gitpod ex-employee complain about high latency pain within your team (in Asia Pacific or Oceania) . What I really can't understand is that this requirement is to simply deploy an additional k8s cluster in another data center of GCP, but the gitpod team seems to have no motivation to do this at all. Is it because the number of users in APAC is too small to be profitable？

This is exactly right. I switched back to mostly local development because gitpod is just too slow. It's actually been two years since this was original promised.

bbhxwl · 2022-11-17T01:46:04Z

Although I bought a one-year license, I didn't use it for an hour. There will be no renewal later.

atduarte · 2022-11-17T13:50:09Z

Thank you @xzmeng, @bbhxwl and @smacintyre for caring so much about Gitpod, and again raising this issue with us—we really do hear your feedback, and we have been discussing internally this issue / feature and how we can make it happen. It’s not easy to see the work that Gitpod is doing behind-the-scenes to progress with issues like this one, but believe us when we say that we’re working towards it. Sadly, it isn’t as straightforward as simply deploying a new cluster. If it were we probably would have shipped this feature already to the community. We really do appreciate your patience, and hopefully we can provide another update soon. Thanks for caring so much about Gitpod and the experience! 🙌

wolf-yuan-6115 · 2022-12-03T14:42:38Z

I am in China and hope to have Hong Kong, Taiwan, Japan or Singapore

I prefer Taiwan because it just at the middle of east Asia

and even GitHub codespaces have Asia server...

modius · 2022-12-06T22:14:01Z

Best latency for my team is australia-southeast1 at <15ms.
Current latency is >150ms for us-west.. couple with that getting test data close enough to make things workable.
Singapore for the record is >100ms here in Sydney.

Australian deployment option would be great.

cloudsbird · 2023-04-26T04:01:58Z

any update on these? it's been 4 months

electrolyte-orb · 2023-05-30T15:49:19Z

asia-south2 would work for our startup ✌️

LouAdrienCEL · 2023-11-27T14:34:09Z

Hey, is there any updates on the ability to chose a region in asia? It's been years in the making now...

LouAdrienCEL · 2024-05-02T10:59:47Z

Hey guys, any news? That's been years now... We are abandoning gitpod because of this, quite sad.

bbhxwl · 2024-05-02T14:03:28Z

Hey guys, any news? That's been years now... We are abandoning gitpod because of this, quite sad.

I have already given up, and I also need Asia

electrolyte-orb · 2024-05-02T15:45:06Z

@LouAdrienCEL GitHub Codespaces offer regional servers... Just sayin

LouAdrienCEL · 2024-05-02T16:16:11Z

@electrolyte-orb thanks for the feedback! Yes aware of codespace (that's actually what we are moving to), but they are tightly coupled with github, while we are on bitbucket. So would have prefered a tool that is more platform agnostic!

Cheers

electrolyte-orb · 2024-05-02T16:24:27Z

@LouAdrienCEL not a big deal... Create a custom dockerfile that automatically checks in bitbucket repo on boot

kylos101 added the type: epic label Jan 6, 2022

csweichel changed the title ~~More regional workspace clusters~~ Epic: more regional workspace clusters Jan 6, 2022

svenefftinge added the team: workspace Issue belongs to the Workspace team label Jan 20, 2022

kylos101 mentioned this issue Feb 28, 2022

Port XXXX Not Found -- The constant need to clear gitpod cookies #8206

Closed

This was referenced Jun 27, 2022

Extremely poor connection for SEA region and CORs error #10920

Closed

Epic: Prebuilds only available in user-specified regions #11055

Open

This was referenced Jul 25, 2022

Gitpod Singapore (sg) region #5534

Closed

Gitpod in Mumbai region #6139

Closed

ghuntley mentioned this issue Jul 29, 2022

Support for MOSH would yield better SSH developer experience #11736

Closed

stale bot added the meta: stale This issue/PR is stale and will be closed soon label Aug 11, 2022

loujaybee mentioned this issue Aug 15, 2022

Investigate reported performance of JetBrains #8704

Closed

gtsiolis mentioned this issue Aug 26, 2022

Epic: SaaS Availability Zone in Asia #12429

Closed

2 tasks

axonasif added meta: never-stale This issue can never become stale and removed meta: stale This issue/PR is stale and will be closed soon labels Aug 29, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Epic: more regional workspace clusters #7489

Epic: more regional workspace clusters #7489

kylos101 commented Jan 6, 2022 •

edited by axonasif

Loading

atduarte commented Feb 4, 2022 •

edited

Loading

Pothulapati commented Feb 8, 2022 •

edited

Loading

andymac4182 commented Feb 17, 2022 •

edited

Loading

bbhxwl commented May 11, 2022

stale bot commented Aug 11, 2022

andymac4182 commented Aug 29, 2022

ghuntley commented Sep 8, 2022

pawlean commented Sep 8, 2022

loujaybee commented Sep 8, 2022 •

edited

Loading

robguy21 commented Oct 13, 2022

xzmeng commented Nov 17, 2022

bbhxwl commented Nov 17, 2022

smacintyre commented Nov 17, 2022

bbhxwl commented Nov 17, 2022

atduarte commented Nov 17, 2022 •

edited

Loading

wolf-yuan-6115 commented Dec 3, 2022 •

edited

Loading

modius commented Dec 6, 2022

cloudsbird commented Apr 26, 2023

electrolyte-orb commented May 30, 2023

LouAdrienCEL commented Nov 27, 2023

LouAdrienCEL commented May 2, 2024

bbhxwl commented May 2, 2024

electrolyte-orb commented May 2, 2024

LouAdrienCEL commented May 2, 2024

electrolyte-orb commented May 2, 2024

Epic: more regional workspace clusters #7489

Epic: more regional workspace clusters #7489

Comments

kylos101 commented Jan 6, 2022 • edited by axonasif Loading

Summary

Context

Value

Acceptance criteria

Measurement

Growth Area

Hypothesis

Complexities

Related

atduarte commented Feb 4, 2022 • edited Loading

Pothulapati commented Feb 8, 2022 • edited Loading

andymac4182 commented Feb 17, 2022 • edited Loading

bbhxwl commented May 11, 2022

stale bot commented Aug 11, 2022

andymac4182 commented Aug 29, 2022

ghuntley commented Sep 8, 2022

pawlean commented Sep 8, 2022

loujaybee commented Sep 8, 2022 • edited Loading

robguy21 commented Oct 13, 2022

xzmeng commented Nov 17, 2022

bbhxwl commented Nov 17, 2022

smacintyre commented Nov 17, 2022

bbhxwl commented Nov 17, 2022

atduarte commented Nov 17, 2022 • edited Loading

wolf-yuan-6115 commented Dec 3, 2022 • edited Loading

modius commented Dec 6, 2022

cloudsbird commented Apr 26, 2023

electrolyte-orb commented May 30, 2023

LouAdrienCEL commented Nov 27, 2023

LouAdrienCEL commented May 2, 2024

bbhxwl commented May 2, 2024

electrolyte-orb commented May 2, 2024

LouAdrienCEL commented May 2, 2024

electrolyte-orb commented May 2, 2024

kylos101 commented Jan 6, 2022 •

edited by axonasif

Loading

atduarte commented Feb 4, 2022 •

edited

Loading

Pothulapati commented Feb 8, 2022 •

edited

Loading

andymac4182 commented Feb 17, 2022 •

edited

Loading

loujaybee commented Sep 8, 2022 •

edited

Loading

atduarte commented Nov 17, 2022 •

edited

Loading

wolf-yuan-6115 commented Dec 3, 2022 •

edited

Loading